Triple
T31472971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1973 London Bridge |
E802907
|
entity |
| Predicate | replacedBridgeSoldTo |
P192575
|
FINISHED |
| Object | Lake Havasu City, Arizona |
—
|
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: Lake Havasu City, Arizona | Statement: [1973 London Bridge, replacedBridgeSoldTo, Lake Havasu City, Arizona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedBridgeSoldTo Context triple: [1973 London Bridge, replacedBridgeSoldTo, Lake Havasu City, Arizona]
-
A.
bridgeReplaced
Indicates that one bridge has been substituted or exchanged for another, typically as a result of construction, repair, or upgrade.
-
B.
originalBridgeRenamed
Indicates that a bridge has undergone a name change from its original designation to a new one.
-
C.
bridgeRebuilt
Indicates that a previously existing bridge has been reconstructed or restored after damage, destruction, or disuse.
-
D.
originalBridgeDestroyed
Indicates that the initially existing bridge in a given context has been destroyed.
-
E.
bridgedFrom
Indicates that something serves as a connection or transition originating from a specified source or starting point.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
| PDg | Predicate description generation | batch_69fd19f6a7888190aa7eee2b87687c53 |
completed | May 7, 2026, 11:02 p.m. |
Created at: April 30, 2026, 9:27 p.m.