Triple
T12328586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnac |
E293898
|
entity |
| Predicate | stoneAlignmentsEstimatedDate |
P877
|
FINISHED |
| Object | c. 4500–3300 BCE |
—
|
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. 4500–3300 BCE | Statement: [Carnac, stoneAlignmentsEstimatedDate, c. 4500–3300 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stoneAlignmentsEstimatedDate Context triple: [Carnac, stoneAlignmentsEstimatedDate, c. 4500–3300 BCE]
-
A.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
B.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
C.
estimatedStartDate
Indicates the date on which something is expected or planned to begin, based on current information or projections.
-
D.
approximateAscentTime
Indicates the estimated amount of time required for an entity to ascend or climb to a specified point or elevation.
-
E.
archCompletionDate
Indicates the date on which an architectural element, project, or structure was completed.
- 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec5be788190b82d2edc6a0f1095 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.