Triple
T34131564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pontia (bridge) |
E875437
|
entity |
| Predicate | isPrincipalBridgeOver |
P386
|
FINISHED |
| Object | Meuse River at Huy |
—
|
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: Meuse River at Huy | Statement: [Pontia (bridge), isPrincipalBridgeOver, Meuse River at Huy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrincipalBridgeOver Context triple: [Pontia (bridge), isPrincipalBridgeOver, Meuse River at Huy]
-
A.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
B.
isMainRoadBridgeOf
Indicates that a bridge serves as the primary or main road crossing associated with a particular road segment or route.
-
C.
hasBridgeTypeCrossing
Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
-
D.
hasMajorBridge
chosen
Indicates that one entity possesses or includes a primary or significant bridge associated with it.
-
E.
isMovableBridge
Indicates that a bridge is designed to move (e.g., lift, swing, or open) to allow passage of traffic such as ships or boats.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 1, 2026, 1:53 a.m.