Triple
T3188422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newburgh–Beacon Bridge |
E66757
|
entity |
| Predicate | isPairOf |
P46528
|
FINISHED |
| Object | parallel bridges |
—
|
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: parallel bridges | Statement: [Newburgh–Beacon Bridge, isPairOf, parallel bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPairOf Context triple: [Newburgh–Beacon Bridge, isPairOf, parallel bridges]
-
A.
dualPair
Indicates that two entities form a dual pair, standing in a mathematically defined dual relationship where each is the dual counterpart of the other.
-
B.
starPairing
Indicates a relationship where two stars are associated or grouped together as a pair, typically for observational, analytical, or classificatory purposes.
-
C.
usesPairsForTransmit
Indicates that an entity performs transmission by utilizing paired elements (such as wires, channels, or signals) as the medium or mechanism for sending information or energy.
-
D.
parityWith
Indicates that two entities share the same parity, such as both being even or both being odd.
-
E.
pairBond
Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
- F. None of above. chosen
Provenance (4 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_69ad8587c1bc8190a2595f2c22ee1001 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6e491508190bc881feaee3889bc |
completed | March 8, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ad9e04290481909092ddfbe6fdaabc |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada148e9108190b363dd0f1a94ac8e |
completed | March 8, 2026, 4:18 p.m. |
Created at: March 8, 2026, 3:06 p.m.