Triple
T14133286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulfstream G600 |
E350222
|
entity |
| Predicate | easaCertificationDate |
P2256
|
FINISHED |
| Object | 2019-10-09 |
—
|
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-10-09 | Statement: [Gulfstream G600, easaCertificationDate, 2019-10-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: easaCertificationDate Context triple: [Gulfstream G600, easaCertificationDate, 2019-10-09]
-
A.
certificationDate
chosen
Indicates the date on which an entity was officially certified or granted a formal certification.
-
B.
lastCrewedFlightDate
Indicates the calendar date on which an aircraft, spacecraft, or similar vehicle was most recently operated with a human crew onboard.
-
C.
EMAAuthorizationDate
Indicates the date on which authorization was granted by the European Medicines Agency (EMA).
-
D.
safetyCertificate
Indicates that an entity has been issued an official certification confirming it meets specified safety standards or regulations.
-
E.
airOperatorCertificateStatus
Indicates the current regulatory approval state of an air operator’s certificate authorizing it to conduct aviation operations.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610cece88190b4a86500677e5938 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 11:34 p.m.