Triple
T31293129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saul |
E797998
|
entity |
| Predicate | hasTransportFeatureNearby |
P124983
|
FINISHED |
| Object | canal junction |
—
|
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: canal junction | Statement: [Saul, hasTransportFeatureNearby, canal junction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransportFeatureNearby Context triple: [Saul, hasTransportFeatureNearby, canal junction]
-
A.
hasTransportationProximityTo
Indicates that one entity is located near or conveniently accessible to another entity in terms of transportation options or routes.
-
B.
hasNearbyInfrastructureType
chosen
Indicates that an entity is located close to infrastructure of a specified type.
-
C.
hasNearbyMode
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
-
D.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
E.
hasTransportationElement
Indicates that one entity includes, involves, or is associated with a specific transportation-related component or feature.
- 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_69f224dfde288190af313f3c221c857e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: April 29, 2026, 9:14 p.m.