Triple
T29430088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hexamilion wall |
E746403
|
entity |
| Predicate | constructedAcross |
P166011
|
FINISHED |
| Object | Isthmus of Corinth |
—
|
NE NERFINISHED |
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: Isthmus of Corinth | Statement: [Hexamilion wall, constructedAcross, Isthmus of Corinth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructedAcross Context triple: [Hexamilion wall, constructedAcross, Isthmus of Corinth]
-
A.
builtAcross
chosen
Indicates that one entity is constructed so that it spans from one side of another entity to the other side, crossing over or covering it.
-
B.
across
Indicates a spatial relationship where one entity is on the opposite side of, or extending from one side to the other side of, another entity or area.
-
C.
constructedTo
Indicates that one entity has been built, created, or designed for the purpose of serving, supporting, or enabling another entity.
-
D.
createdByCrossing
Indicates that something was produced as a result of crossing or hybridizing two or more distinct entities.
-
E.
constructedAs
Indicates that one entity is built, formed, or created in the manner, structure, or configuration specified by 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 28, 2026, 3:12 p.m.