Triple
T542118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multnomah Falls |
E12652
|
entity |
| Predicate | bridgeLocation |
P15474
|
FINISHED |
| Object | between upper and lower tiers |
—
|
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: between upper and lower tiers | Statement: [Multnomah Falls, bridgeLocation, between upper and lower tiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeLocation Context triple: [Multnomah Falls, bridgeLocation, between upper and lower tiers]
-
A.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
-
B.
bridges
Indicates that one entity connects or links two or more other entities, allowing passage, transition, or interaction between them.
-
C.
bridgeheadEstablished
Indicates that a secure initial position or foothold has been successfully created and held in a new or contested area, enabling further expansion or operations.
-
D.
hasMajorBridge
Indicates that one entity possesses or includes a primary or significant bridge associated with it.
-
E.
otherMainBridge
Indicates that one bridge serves as an alternative or secondary primary bridge in relation to another main bridge.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49861195081909540eaf402a5401a |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b8098481908097228db8ad0262 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49858abd48190bd4b002a93e4a908 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.