Triple
T37322189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teyuna |
E926511
|
entity |
| Predicate | firstArchaeologicalWorkYear |
P86848
|
FINISHED |
| Object | 1976 |
—
|
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: 1976 | Statement: [Teyuna, firstArchaeologicalWorkYear, 1976]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstArchaeologicalWorkYear Context triple: [Teyuna, firstArchaeologicalWorkYear, 1976]
-
A.
firstExcavationYear
chosen
Indicates the calendar year in which an excavation activity at a given site or object was first carried out.
-
B.
earliestArchaeologicalCulture
Indicates that one archaeological culture is the earliest known or first in time within a specified sequence, region, or context.
-
C.
excavationYear
Indicates the year in which an excavation activity took place or was conducted.
-
D.
estimatedYearOfCreation
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
-
E.
earliestConstructionAttributedTo
Indicates that one entity is recognized as the earliest known construction project or built work attributed to another entity (such as a person, group, or organization).
- 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.