Triple
T32956478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office Bridge |
E843114
|
entity |
| Predicate | isLongestCoveredBridgeIn |
P147719
|
FINISHED |
| Object | Oregon |
—
|
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: Oregon | Statement: [Office Bridge, isLongestCoveredBridgeIn, Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLongestCoveredBridgeIn Context triple: [Office Bridge, isLongestCoveredBridgeIn, Oregon]
-
A.
wasLongestCoveredWoodenBridge
chosen
Indicates that the subject held the status of being the longest covered wooden bridge within a given scope or time period.
-
B.
wasWorldsLongestSuspensionBridgeSpan
Indicates that something held the record for having the longest main span of any suspension bridge in the world at a given time.
-
C.
isOldestSurvivingBridgeAcross
Indicates that a bridge is the most ancient still-existing bridge that spans a specified waterway, road, or gap.
-
D.
wasWorldsLongestConcreteArchSpan
Indicates that something held the record for being the world's longest concrete arch span.
-
E.
bridgeSpans
Indicates that a bridge extends across and connects two separate points or areas.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d175fc988190ad4872c9b647b71d |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.