Triple
T33515687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vickers Viscount |
E858358
|
entity |
| Predicate | enteredCommercialService |
P148888
|
FINISHED |
| Object | 1953-04-18 |
—
|
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: 1953-04-18 | Statement: [Vickers Viscount, enteredCommercialService, 1953-04-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredCommercialService Context triple: [Vickers Viscount, enteredCommercialService, 1953-04-18]
-
A.
enteredService
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
B.
enteredServiceOn
chosen
Indicates the date or time when an entity first began active use, operation, or service.
-
C.
enteredServiceInCity
Indicates that an entity began its operational service or official use within a specified city.
-
D.
enteredServiceWithUnit
Indicates that an entity began its period of service or active duty while assigned to a specified unit.
-
E.
enteredServiceBefore
Indicates that one entity began its period of service earlier in time than 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 1:39 a.m.