Triple
T478900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nazca Lines |
E9122
|
entity |
| Predicate | approximateConstructionEnd |
P8204
|
FINISHED |
| Object | c. 500 CE |
—
|
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: c. 500 CE | Statement: [Nazca Lines, approximateConstructionEnd, c. 500 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateConstructionEnd Context triple: [Nazca Lines, approximateConstructionEnd, c. 500 CE]
-
A.
hasApproximateEnd
chosen
Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
-
B.
constructionTime
Indicates the duration or specific point in time required to construct or build an entity.
-
C.
constructionCompleted
Indicates that a construction process or project has been fully finished and reached its completed state.
-
D.
hasApproximateDuration
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
E.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
- 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.