Triple
T21721804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Never Too Far |
E536175
|
entity |
| Predicate | bridgeFeature |
P145091
|
FINISHED |
| Object | modulation key change |
—
|
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: modulation key change | Statement: [Never Too Far, bridgeFeature, modulation key change]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeFeature Context triple: [Never Too Far, bridgeFeature, modulation key change]
-
A.
bridgeComponent
Indicates that one entity functions as a structural or functional component of a bridge associated with another entity.
-
B.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
C.
bridgeName
Indicates the designated name assigned to a specific bridge.
-
D.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
-
E.
bridgeModel
Indicates a relationship where one entity serves as an intermediate model or representation that connects or translates between two other entities or systems.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd97032c08190820b87a288e77293 |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:47 p.m.