Triple
T2824677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adria Airways |
E54891
|
entity |
| Predicate | ceasedOperationsDate |
P17360
|
FINISHED |
| Object | 2019-09-30 |
—
|
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-09-30 | Statement: [Adria Airways, ceasedOperationsDate, 2019-09-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasedOperationsDate Context triple: [Adria Airways, ceasedOperationsDate, 2019-09-30]
-
A.
ceasedActivityUnder
Indicates that an entity stopped performing a particular activity while under the authority, influence, or conditions imposed by another entity.
-
B.
ceasedOperation
chosen
Indicates that an entity has stopped functioning, operating, or carrying out its activities, typically in a permanent or indefinite manner.
-
C.
ceaseToExistDecisionDate
Indicates the date on which a formal decision was made that something will cease to exist or be terminated.
-
D.
retirementDate
Indicates the date on which an entity stops its active role or service, typically marking the end of its professional or operational period.
-
E.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active 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_69ab49e100c0819082a40cb797383243 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abdf15b7288190a03d1193cc0544a6 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd08f2f481908c3da8a9c7a00552 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.