Triple
T1032367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dodona |
E22279
|
entity |
| Predicate | archaeologicalExcavationsBegan |
P7651
|
FINISHED |
| Object | late 19th 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: late 19th century | Statement: [Dodona, archaeologicalExcavationsBegan, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archaeologicalExcavationsBegan Context triple: [Dodona, archaeologicalExcavationsBegan, late 19th century]
-
A.
majorExcavationsBegan
chosen
Indicates that significant archaeological or construction excavation work was initiated at a particular time or for a particular project.
-
B.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
C.
excavatedBy
Indicates that something (typically an archaeological site, artifact, or geological feature) was uncovered or dug out by a particular agent (such as a person, team, or organization).
-
D.
archaeologicalFindsInclude
Indicates that the set of archaeological finds at a site or context contains or encompasses the specified items or types of artifacts.
-
E.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
- 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_69a493d848848190aed4011b34b2e8d3 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8d669448190955507e2e4975b9f |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b728ad3481909cf1430349cb9bba |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.