Triple
T25059356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antirrio |
E627612
|
entity |
| Predicate | bridgeTerminusOf |
P97300
|
FINISHED |
| Object | Charilaos Trikoupis Bridge |
—
|
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: Charilaos Trikoupis Bridge | Statement: [Antirrio, bridgeTerminusOf, Charilaos Trikoupis Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeTerminusOf Context triple: [Antirrio, bridgeTerminusOf, Charilaos Trikoupis Bridge]
-
A.
locatedAtTerminusOf
Indicates that one entity is situated at the end point or final terminus of another entity, such as a route, line, or path.
-
B.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
C.
connectsTerminus
chosen
Indicates that one entity serves as a terminus that is directly linked or joined to another entity.
-
D.
bridgesBetween
Indicates a relationship where something connects or links two otherwise separate entities, contexts, or states, enabling interaction or transition between them.
-
E.
terminusJunction
Indicates a relationship where a route, line, or path ends at a junction point that serves as its terminal connection.
- 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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f45997ff78819082a60f81f9a88064 |
completed | May 1, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:09 a.m.