Triple
T37694109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles River Bridge |
E938880
|
entity |
| Predicate | competingStructure |
P1375
|
FINISHED |
| Object | Warren 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: Warren Bridge | Statement: [Charles River Bridge, competingStructure, Warren Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competingStructure Context triple: [Charles River Bridge, competingStructure, Warren Bridge]
-
A.
competesWith
chosen
Indicates that two entities are in rivalry or opposition, each striving to outperform or gain advantage over the other in the same domain or objective.
-
B.
competingStandard
Indicates that one standard exists in rivalry or conflict with another standard, typically addressing the same need or domain in an incompatible or alternative way.
-
C.
competitiveFunction
Indicates a relationship where one entity performs a function or role that directly competes with, or serves as a rival to, the function performed by another entity.
-
D.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
E.
competitorDesign
Indicates that one entity has designed or created something that competes with a design or product of another entity.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: May 3, 2026, 4:18 p.m.