Triple
T12111618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Udu |
E288443
|
entity |
| Predicate | UduBridgeConnects |
P36619
|
FINISHED |
| Object | Udu to Warri |
—
|
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: Udu to Warri | Statement: [Udu, UduBridgeConnects, Udu to Warri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UduBridgeConnects Context triple: [Udu, UduBridgeConnects, Udu to Warri]
-
A.
hasBridgeTo
chosen
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
B.
isUrbanBridge
Indicates that a bridge is located within or closely associated with an urban (city or town) environment.
-
C.
bridgesBetween
Indicates a relationship where something connects or links two otherwise separate entities, contexts, or states, enabling interaction or transition between them.
-
D.
bridgeUsed
Indicates that a bridge is utilized or traversed by an entity to cross between two locations or points.
-
E.
hasNearbyBridge
Indicates that one entity is located close to a bridge associated with or relevant to it.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9164ada5081908676bd9e5947268a |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150497408190921334d21503375a |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.