Triple
T38053283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Choquequirao |
E949827
|
entity |
| Predicate | firstEuropeanDocumentationCentury |
P196110
|
FINISHED |
| Object | 17th 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: 17th century | Statement: [Choquequirao, firstEuropeanDocumentationCentury, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEuropeanDocumentationCentury Context triple: [Choquequirao, firstEuropeanDocumentationCentury, 17th century]
-
A.
firstReportedCentury
chosen
Indicates the century in which something was first reported or documented.
-
B.
firstPerformedCentury
Indicates the century in which an action, work, or performance was first carried out or presented.
-
C.
attestedUntilCentury
Indicates the latest century up to which the existence or use of something is historically documented or evidenced.
-
D.
earlyEuropeanPresence
Indicates the existence or establishment of Europeans in a place or context during an initial or formative historical period.
-
E.
firstDocumentedEuropeanCrossingOf
Indicates that the subject is credited with making the first recorded crossing of the object by a European.
- 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_69f76f000cf081908c11fb5443b392e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.