Triple
T29848419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairlop tube station |
E757995
|
entity |
| Predicate | enteredCentralLineService |
P174294
|
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: [Fairlop tube station, enteredCentralLineService, 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredCentralLineService Context triple: [Fairlop tube station, enteredCentralLineService, 1948]
-
A.
enteredService
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
B.
enteredServiceOnLine14
Indicates that an entity (such as a vehicle or piece of equipment) began operating in regular service on route or line 14.
-
C.
enteredServiceWithUnit
Indicates that an entity began its period of service or active duty while assigned to a specified unit.
-
D.
enteredANGService
Indicates that an entity has begun or been inducted into service within the ANG (Air National Guard).
-
E.
enteredServiceOn
Indicates the date or time when an entity first began active use, operation, or service.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69f6bbf5a8288190ae170bcbe8ab65cf |
completed | May 3, 2026, 3:07 a.m. |
Created at: April 29, 2026, 5:42 p.m.