Triple
T478850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Machu Picchu |
E9121
|
entity |
| Predicate | rediscoveryDate |
P3836
|
FINISHED |
| Object | 1911 |
—
|
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: 1911 | Statement: [Machu Picchu, rediscoveryDate, 1911]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rediscoveryDate Context triple: [Machu Picchu, rediscoveryDate, 1911]
-
A.
discoveryDate
chosen
Indicates the date on which something was first discovered or identified.
-
B.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
C.
rededicationDate
Indicates the date on which something is formally dedicated again, typically after restoration, change, or renewal.
-
D.
reestablishedInYear
Indicates that an entity, previously existing and then discontinued or dissolved, was brought back into existence or operation in the specified year.
-
E.
reconstructionOrRestorationDate
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f056459881909749764cc4a7f9e8 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf1d5848190a7da27e2fddc136f |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.