Triple
T26241290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfursan Gold |
E656320
|
entity |
| Predicate | serviceClassCompatibility |
P48645
|
FINISHED |
| Object | economy class |
—
|
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: economy class | Statement: [Alfursan Gold, serviceClassCompatibility, economy class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceClassCompatibility Context triple: [Alfursan Gold, serviceClassCompatibility, economy class]
-
A.
checksCompatibilityWith
Indicates that one entity evaluates whether it is compatible or can function harmoniously with another entity.
-
B.
automationCompatibility
Indicates that one entity can be reliably and effectively operated, controlled, or integrated through automated systems or processes in relation to another entity.
-
C.
isGenerallyCompatibleWith
chosen
Indicates that two entities can typically function or coexist together without significant conflict, issues, or need for special adaptation.
-
D.
claimsCompatibilityWith
Indicates that one entity asserts it is compatible or can work harmoniously with another entity.
-
E.
scopeCompatibility
Indicates that two elements can coexist or interact within the same scope or contextual boundary without conflict.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 26, 2026, 9:03 p.m.