Triple
T10413831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAP Miles&Go Gold |
E245462
|
entity |
| Predicate | statusRecognitionBy |
P59271
|
FINISHED |
| Object | all Star Alliance member airlines |
—
|
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: all Star Alliance member airlines | Statement: [TAP Miles&Go Gold, statusRecognitionBy, all Star Alliance member airlines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusRecognitionBy Context triple: [TAP Miles&Go Gold, statusRecognitionBy, all Star Alliance member airlines]
-
A.
recognitionStatus
Indicates the current state or outcome of acknowledging, validating, or officially accepting something or someone.
-
B.
recognizesStatus
chosen
Indicates that one entity acknowledges or accepts the official status or standing of another entity.
-
C.
recognizedSee
Indicates that one entity sees another and consciously recognizes or identifies what is being seen.
-
D.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
E.
statusRecordedBy
Indicates that the status of an entity was documented or captured by a specific agent or system.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea0ec6fc8190a71af759226a3cba |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:10 p.m.