Triple
T1642693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longfellow Bridge |
E35507
|
entity |
| Predicate | underwentMajorRehabilitation |
P24909
|
FINISHED |
| Object | 2013–2018 |
—
|
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: 2013–2018 | Statement: [Longfellow Bridge, underwentMajorRehabilitation, 2013–2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underwentMajorRehabilitation Context triple: [Longfellow Bridge, underwentMajorRehabilitation, 2013–2018]
-
A.
dateOfRehabilitation
Indicates the specific date on which a rehabilitation process, status, or measure for an entity was completed, granted, or took effect.
-
B.
largelyRebuilt
Indicates that an entity has been substantially reconstructed or renovated, with most of its original structure replaced or significantly altered.
-
C.
underwent
Indicates that an entity experienced or was subjected to a process, event, or change, typically as the patient of an action.
-
D.
hasReconstructionWork
Indicates that an entity is undergoing, has undergone, or is associated with reconstruction or restoration work.
-
E.
reconstructedDuring
chosen
Indicates that an entity was rebuilt, restored, or significantly repaired within a specified time period or event.
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a919306fd48190a245fc95e0e759d9 |
completed | March 5, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69a907cc9d348190b76b0d3f596e5a81 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.