Triple
T2248303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Alliance Silver |
E49556
|
entity |
| Predicate | statusRecognition |
P21446
|
FINISHED |
| Object | alliance-wide |
—
|
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: alliance-wide | Statement: [Star Alliance Silver, statusRecognition, alliance-wide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusRecognition Context triple: [Star Alliance Silver, statusRecognition, alliance-wide]
-
A.
recognitionStatus
chosen
Indicates the current state or outcome of acknowledging, validating, or officially accepting something or someone.
-
B.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
C.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
D.
identityStatus
Indicates the current state or condition of an entity’s identity, such as whether it is verified, active, pending, or otherwise classified.
-
E.
statusWordRegister
Indicates the level of formality or social register associated with a status-related word in language use.
- 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_69a88aa979788190ad6500f1d8eee2fc |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0ed5c38819080b45ea398fb59f2 |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69abbdb160248190aa75b38f11ad8602 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.