Triple
T26931560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 317 |
E678236
|
entity |
| Predicate | refurbishmentFeatures |
P8964
|
FINISHED |
| Object | new seating |
—
|
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 seating | Statement: [British Rail Class 317, refurbishmentFeatures, new seating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refurbishmentFeatures Context triple: [British Rail Class 317, refurbishmentFeatures, new seating]
-
A.
renovationFeature
chosen
Indicates that an entity has a specific renovation-related characteristic, element, or improvement associated with it.
-
B.
refurbishedIn
Indicates that an entity has undergone restoration, repair, or renovation at a specific time or during a particular period.
-
C.
refurbishedAs
Indicates that an entity has been renovated, restored, or upgraded and subsequently used or designated in a new or improved form or function.
-
D.
renovationOccasion
Indicates the event, reason, or context that serves as the occasion for a renovation to take place.
-
E.
requiresRenovation
Indicates that an entity is in a condition that necessitates repair, updating, or refurbishment before it is suitable for normal use or standards.
- 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f620497848819087881b4f82c7bc22 |
completed | May 2, 2026, 4:03 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:13 a.m.