Triple
T24004073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Bridge |
E594323
|
entity |
| Predicate | wasRebuiltInYear |
P9623
|
FINISHED |
| Object | 1345 |
—
|
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: 1345 | Statement: [Old Bridge, wasRebuiltInYear, 1345]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRebuiltInYear Context triple: [Old Bridge, wasRebuiltInYear, 1345]
-
A.
rebuiltApproximateEndYear
Indicates that an entity was rebuilt, with the specified year representing an approximate (not exact) end date of the rebuilding process.
-
B.
reconstructionYear
chosen
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
-
C.
rebuiltOrModifiedDuring
Indicates that an existing entity was reconstructed, renovated, or otherwise significantly altered during a specified time period or event.
-
D.
rebuiltOn
Indicates that one entity has been reconstructed, restored, or built again on, over, or using the foundation, structure, or basis of another entity.
-
E.
rebuiltBetween
Indicates that an entity was reconstructed or rebuilt during a time interval bounded by two specified temporal points.
- 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_69e288b9ecf08190b8c94a278f5674fe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d467108481909e33de1c7319738a |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:40 p.m.