Triple
T28537887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matmid Silver |
E722216
|
entity |
| Predicate | statusProgramOperator |
P66068
|
FINISHED |
| Object | EL AL Israel Airlines |
—
|
NE NERFINISHED |
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: EL AL Israel Airlines | Statement: [Matmid Silver, statusProgramOperator, EL AL Israel Airlines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusProgramOperator Context triple: [Matmid Silver, statusProgramOperator, EL AL Israel Airlines]
-
A.
operatorStatus
chosen
Indicates the current operational state or condition of an operator (e.g., active, inactive, or in error).
-
B.
programStatus
Indicates the current state or condition of a program within its lifecycle (e.g., planned, active, paused, completed, or terminated).
-
C.
operatingStatus
Indicates whether an entity is currently functioning, active, or in service versus inactive, closed, or out of service.
-
D.
statusProgramRegion
Indicates the current state or condition of a program within a specific geographic or administrative region.
-
E.
statusInterface
Indicates that an entity serves as, or is associated with, an interface that reports or reflects its current status.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 28, 2026, 3:33 a.m.