Triple
T33911581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EB Diamond |
E869327
|
entity |
| Predicate | airlineCodeContext |
P177902
|
FINISHED |
| Object | SK |
—
|
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: SK | Statement: [EB Diamond, airlineCodeContext, SK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineCodeContext Context triple: [EB Diamond, airlineCodeContext, SK]
-
A.
airlineContext
Indicates a relationship, situation, or action that specifically occurs within or is constrained by an airline-related context (such as flights, carriers, or air travel operations).
-
B.
airlineServicePattern
Indicates the characteristic way an airline operates its services, such as the routes, frequencies, and scheduling patterns it follows between locations.
-
C.
planeCode
Indicates that an entity is associated with a specific identifying code assigned to a plane.
-
D.
airlineService
Indicates that an airline operates transportation services (such as flights) between specified locations or for specified routes.
-
E.
airportCodeContext
Indicates that an airport code is being used or interpreted within a specific contextual framework (such as a region, system, or standard) that defines its meaning.
- F. None of above. chosen
Provenance (4 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f70519f114819080659840c04d7911 |
completed | May 3, 2026, 8:19 a.m. |
Created at: May 1, 2026, 1:48 a.m.