Triple
T21804454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark 4 coaching stock |
E538313
|
entity |
| Predicate | enteredRefurbishment |
P86076
|
FINISHED |
| Object | 2000s |
—
|
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: 2000s | Statement: [Mark 4 coaching stock, enteredRefurbishment, 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredRefurbishment Context triple: [Mark 4 coaching stock, enteredRefurbishment, 2000s]
-
A.
refurbishedIn
chosen
Indicates that an entity has undergone restoration, repair, or renovation at a specific time or during a particular period.
-
B.
renovationOccasion
Indicates the event, reason, or context that serves as the occasion for a renovation to take place.
-
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.
rebuiltInterior
Indicates that the interior of an entity has been reconstructed or significantly renovated, typically after damage, aging, or redesign.
-
E.
useAfterRenovation
Indicates that something is intended to be used or occupied only after renovation work has been completed.
- 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07801fa8081909098d00947bf8f7f |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:53 p.m.