Triple
T13169089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridge Day |
E312927
|
entity |
| Predicate | bridgeHeightUsed |
P108866
|
FINISHED |
| Object | approximately 876 feet |
—
|
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: approximately 876 feet | Statement: [Bridge Day, bridgeHeightUsed, approximately 876 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeHeightUsed Context triple: [Bridge Day, bridgeHeightUsed, approximately 876 feet]
-
A.
bridgeUsed
Indicates that a bridge is utilized or traversed by an entity to cross between two locations or points.
-
B.
skybridgeHeight
Indicates the vertical distance or clearance between a skybridge and a reference surface (such as the ground or roadway) or between connected structures.
-
C.
bridgePosition
Indicates the spatial or structural position of a bridge relative to other referenced elements or locations.
-
D.
bridgeCapacity
Indicates the maximum load or volume that a bridge can safely support or accommodate.
-
E.
bridgeLength
Indicates the physical length or span of a bridge structure.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98ceeb22c8190a6be666031d9e5a4 |
completed | April 10, 2026, 11:51 p.m. |
Created at: April 9, 2026, 9:13 p.m.