Triple
T34522881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pucará de Tilcara |
E886323
|
entity |
| Predicate | majorExcavationsStarted |
P7651
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Pucará de Tilcara, majorExcavationsStarted, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorExcavationsStarted Context triple: [Pucará de Tilcara, majorExcavationsStarted, early 20th century]
-
A.
majorExcavationsBegan
chosen
Indicates that significant archaeological or construction excavation work was initiated at a particular time or for a particular project.
-
B.
majorExcavationsDate
Indicates the date or time period when significant excavation activities were carried out on an entity.
-
C.
majorExcavationEndYear
Indicates the year in which a major excavation activity or project was completed.
-
D.
laterExcavationsStart
Indicates that the start of one excavation occurs after the start of another excavation.
-
E.
excavationSite
Indicates a location where digging or removal of earth or materials is actively conducted, typically for construction, mining, or archaeological purposes.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
Created at: May 1, 2026, 2:02 a.m.