Triple
T23737227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galileo programme |
E586570
|
entity |
| Predicate | firstOperationalServicesDate |
P35191
|
FINISHED |
| Object | 2016-12-15 |
—
|
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: 2016-12-15 | Statement: [Galileo programme, firstOperationalServicesDate, 2016-12-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOperationalServicesDate Context triple: [Galileo programme, firstOperationalServicesDate, 2016-12-15]
-
A.
operatorStartDate
Indicates the date on which an operator’s role, activity, or responsibility begins.
-
B.
operatedSince
Indicates that an entity has been in operation continuously from a specified starting time or date.
-
C.
firstLineOpeningDate
Indicates the date on which the first line in a system, network, or service was officially opened or began operation.
-
D.
initiallyOperated
Indicates that an entity first began functioning, being used, or carrying out its intended operation at a specified initial time or under initial conditions.
-
E.
openedForCommercialService
chosen
Indicates that something (such as a facility, route, or service) began operating and became available for regular commercial use.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad28fa481909d7a6a6e98a7b0a5 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:10 p.m.