Triple
T22468807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Street Bridge |
E555432
|
entity |
| Predicate | reconstructionIncluded |
P61459
|
FINISHED |
| Object | new lighting |
—
|
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: new lighting | Statement: [South Street Bridge, reconstructionIncluded, new lighting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reconstructionIncluded Context triple: [South Street Bridge, reconstructionIncluded, new lighting]
-
A.
reconstructedIn
Indicates that something has been rebuilt, restored, or re-created within a particular context, location, or medium.
-
B.
containsReconstructionOf
chosen
Indicates that one entity includes or incorporates a recreated, restored, or reconstructed version of another entity.
-
C.
reconstructedWith
Indicates that something has been rebuilt, restored, or reassembled using a specified method, material, or set of components.
-
D.
involvesReconstructionOf
Indicates that one entity includes, requires, or performs the rebuilding, restoration, or re-creation of another entity or its prior state.
-
E.
reconstructionBuilt
Indicates that one entity carried out or was responsible for constructing a rebuilt or restored version of another entity.
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15bdda62c8190937ac13a4481b4b7 |
completed | April 29, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.