Triple
T26810742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tunnel of Eupalinos |
E671984
|
entity |
| Predicate | excavationTechnique |
P126000
|
FINISHED |
| Object | hand tools |
—
|
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: hand tools | Statement: [Tunnel of Eupalinos, excavationTechnique, hand tools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excavationTechnique Context triple: [Tunnel of Eupalinos, excavationTechnique, hand tools]
-
A.
excavatedUsing
chosen
Indicates that an excavation was carried out with the aid of a specified tool, method, or equipment.
-
B.
excavationType
Indicates the specific method or category of excavation associated with an entity or activity.
-
C.
excavationProject
Indicates that an entity is involved in or constitutes a project whose primary activity is the systematic excavation of a site or area.
-
D.
excavationSite
Indicates a location where digging or removal of earth or materials is actively conducted, typically for construction, mining, or archaeological purposes.
-
E.
excavatedAs
Indicates that one entity has been dug out, uncovered, or removed from its surrounding material or context in the form or role of another specified 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 4:29 a.m.