Triple
T5517416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingston Bridge |
E144718
|
entity |
| Predicate | refurbishmentPurpose |
P11548
|
FINISHED |
| Object | strengthening structure |
—
|
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: strengthening structure | Statement: [Kingston Bridge, refurbishmentPurpose, strengthening structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refurbishmentPurpose Context triple: [Kingston Bridge, refurbishmentPurpose, strengthening structure]
-
A.
renovationPurpose
chosen
Indicates that an entity is being renovated with a specific intended goal, use, or outcome in mind.
-
B.
renovationFeature
Indicates that an entity has a specific renovation-related characteristic, element, or improvement associated with it.
-
C.
requiresRenovation
Indicates that an entity is in a condition that necessitates repair, updating, or refurbishment before it is suitable for normal use or standards.
-
D.
renovatedBy
Indicates that an entity has been improved, restored, or updated through renovation work performed by another entity.
-
E.
renovatedFrom
Indicates that one entity has been updated, improved, or restored by modifying or reworking an earlier version represented by 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_69c008f77ff88190b0cd50ca207295d1 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f6cefe48190bfda90d6afab8468 |
completed | March 22, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69c01b0a06348190b39ac9fe80d2836a |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:33 p.m.