Triple
T29953589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LNER Class V2 |
E760834
|
entity |
| Predicate | enteredBRServiceYear |
P174720
|
FINISHED |
| Object | 1948 |
—
|
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: 1948 | Statement: [LNER Class V2, enteredBRServiceYear, 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredBRServiceYear Context triple: [LNER Class V2, enteredBRServiceYear, 1948]
-
A.
enteredServiceApproximateYear
Indicates that an entity began its service or operation around a specified year, where the year is an approximate rather than an exact value.
-
B.
enteredServiceYearWithUSN
Indicates the year in which an entity (such as a vessel or asset) officially entered active service with the United States Navy.
-
C.
accessionYear
Indicates the calendar year in which an item, record, or entity was formally added to or registered within a collection, system, or institution.
-
D.
yearOfManufacture
Indicates the specific calendar year in which an item was produced or manufactured.
-
E.
yearOfUse
Indicates the specific year during which something was in use or actively utilized.
- F. None of above. chosen
Provenance (4 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6c5b7e46081909975b05f7298cc0e |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c49069e48190a3486b6254a6645b |
completed | May 3, 2026, 3:44 a.m. |
Created at: April 29, 2026, 6:26 p.m.