Triple
T11840864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xoloitzcuintle |
E281647
|
entity |
| Predicate | fciSection |
P27372
|
FINISHED |
| Object | Section 6 Primitive type |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Section 6 Primitive type | Statement: [Xoloitzcuintle, fciSection, Section 6 Primitive type]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fciSection Context triple: [Xoloitzcuintle, fciSection, Section 6 Primitive type]
-
A.
section
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
B.
sectionType
chosen
Indicates the specific kind or category of section that an entity belongs to or represents.
-
C.
councilDocumentSectionOf
Indicates that one document section belongs to, or forms a part of, a specific council document.
-
D.
phase1Section
Indicates that something belongs to, occurs within, or is associated with the first phase or section of a larger process or structure.
-
E.
typicalSection
Indicates that one section is a standard, representative, or commonly occurring instance within a broader set or structure of sections.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.