Triple
T19057000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vande Bharat Express |
E466422
|
entity |
| Predicate | firstServiceEntry |
P2339
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Vande Bharat Express, firstServiceEntry, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstServiceEntry Context triple: [Vande Bharat Express, firstServiceEntry, 2019]
-
A.
firstServiceAircraft
Indicates that the subject aircraft is the first of its type to enter operational service with the specified operator or organization.
-
B.
firstRegularServiceStarted
Indicates that the initial instance of a regular, scheduled service or operation began at a specified time.
-
C.
enteredService
chosen
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
D.
primaryService
Indicates that one entity serves as the main or principal service provided or used in relation to another entity.
-
E.
serviceEntryWith
Indicates that one entity is associated with or accompanied by a particular service entry in a joint or linked context.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc067f788190b3b149dfee370435 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.