Triple
T33795814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 76 in North Carolina |
E866070
|
entity |
| Predicate | sharesBridge |
P94314
|
FINISHED |
| Object | Cape Fear Memorial 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: Cape Fear Memorial Bridge | Statement: [U.S. Route 76 in North Carolina, sharesBridge, Cape Fear Memorial Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesBridge Context triple: [U.S. Route 76 in North Carolina, sharesBridge, Cape Fear Memorial Bridge]
-
A.
sharesBridgeWith
chosen
Indicates that two entities use or are connected by the same bridge structure.
-
B.
bridgesBetween
Indicates a relationship where something connects or links two otherwise separate entities, contexts, or states, enabling interaction or transition between them.
-
C.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
D.
bridges
Indicates that one entity connects or links two or more other entities, allowing passage, transition, or interaction between them.
-
E.
sharesBranchWith
Indicates that two entities belong to or operate within the same branch of an organization, structure, or hierarchy.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffc704e1e88190884928a6a5c55a87 |
completed | May 9, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69ffc6b483d881908ad872e25fa6abc5 |
completed | May 9, 2026, 11:43 p.m. |
Created at: May 1, 2026, 1:46 a.m.