Triple
T32090691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pueblo III period |
E819581
|
entity |
| Predicate | positionInPecosClassification |
P44056
|
FINISHED |
| Object | third Pueblo period |
—
|
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: third Pueblo period | Statement: [Pueblo III period, positionInPecosClassification, third Pueblo period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInPecosClassification Context triple: [Pueblo III period, positionInPecosClassification, third Pueblo period]
-
A.
positionClass
Indicates the classification or category assigned to an entity based on its role, rank, or position within a defined structure or system.
-
B.
positionInPermian
Indicates the relative ordering or placement of an element within a specific permutation.
-
C.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
D.
eraClassification
chosen
Indicates the historical era or time period into which an entity is categorized or classified.
-
E.
southernmostClassification
Indicates the classification assigned to the entity that lies furthest to the south among a set of related entities.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: May 1, 2026, 12:25 a.m.