Triple
T3381769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Berlin |
E71201
|
entity |
| Predicate | operatingLicenseStatus |
P17256
|
FINISHED |
| Object | revoked |
—
|
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: revoked | Statement: [Air Berlin, operatingLicenseStatus, revoked]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatingLicenseStatus Context triple: [Air Berlin, operatingLicenseStatus, revoked]
-
A.
operatingStatus
Indicates whether an entity is currently functioning, active, or in service versus inactive, closed, or out of service.
-
B.
franchiseStatus
Indicates the current standing or condition of a franchise relationship between parties, such as whether it is active, inactive, pending, or terminated.
-
C.
regulationStatus
Indicates the regulatory condition or compliance state that applies to an entity under relevant rules or laws.
-
D.
airOperatorCertificateStatus
chosen
Indicates the current regulatory approval state of an air operator’s certificate authorizing it to conduct aviation operations.
-
E.
typeOfLicense
Indicates the specific kind or category of license associated with an 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb5e9af608190bfb228ef99a87bb7 |
completed | March 8, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.