Triple
T11651889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fly Jinnah |
E276922
|
entity |
| Predicate | serviceClassConfiguration |
P5621
|
FINISHED |
| Object | single-class cabin |
—
|
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: single-class cabin | Statement: [Fly Jinnah, serviceClassConfiguration, single-class cabin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceClassConfiguration Context triple: [Fly Jinnah, serviceClassConfiguration, single-class cabin]
-
A.
serviceClass
chosen
Indicates the classification or category of service associated with or provided by an entity in the relationship.
-
B.
serviceClassAccess
Indicates that one entity is permitted to use or interact with a particular class or category of service provided by another entity.
-
C.
serviceComponent
Indicates that one entity functions as a component or sub-part within the structure or implementation of a larger service.
-
D.
serviceNumberOrClass
Indicates that one entity specifies the service identifier or class designation associated with another entity.
-
E.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2d01f9c8190849f252f22519550 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.