Triple
T26810743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tunnel of Eupalinos |
E671984
|
entity |
| Predicate | surveyingMethod |
P14440
|
FINISHED |
| Object | geometric and trigonometric planning |
—
|
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: geometric and trigonometric planning | Statement: [Tunnel of Eupalinos, surveyingMethod, geometric and trigonometric planning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surveyingMethod Context triple: [Tunnel of Eupalinos, surveyingMethod, geometric and trigonometric planning]
-
A.
surveyor
Indicates that an entity performs the role or action of surveying, typically by measuring, inspecting, or assessing something such as land, structures, or conditions.
-
B.
surveyMethod
chosen
Indicates the technique or procedure used to conduct a survey or collect survey data.
-
C.
methodologyType
Indicates the specific kind or category of method or procedure used in carrying out an activity or study.
-
D.
usesSurveyPoint
Indicates that an entity relies on or references a specific survey point as a positional or measurement basis in its activity or relationship.
-
E.
assessmentMethod
Indicates the method or procedure used to evaluate, measure, or judge something.
- 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_69f61a2309508190b88c47908660c015 |
completed | May 2, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 4:29 a.m.