Triple
T25715523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GO-FLY |
E644852
|
entity |
| Predicate | userStatus |
P88146
|
FINISHED |
| Object | former airline |
—
|
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: former airline | Statement: [GO-FLY, userStatus, former airline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userStatus Context triple: [GO-FLY, userStatus, former airline]
-
A.
playerStatus
Indicates the current state or condition of a player within a game or system, such as their activity, health, or participation status.
-
B.
usageStatus
Indicates the current state or condition of how something is being used, such as whether it is active, inactive, available, or in use.
-
C.
exportStatus
Indicates the current state or outcome of an entity’s export process (e.g., pending, in progress, completed, or failed).
-
D.
publicInformationStatus
Indicates whether and to what extent certain information is publicly accessible or disclosed.
-
E.
customStatus
chosen
Indicates that an entity has a user-defined or non-standard status assigned to it.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc6211788190bb46c645902c2bc2 |
completed | May 2, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69f480824a1c81908a8a492eedbc2596 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 9:40 p.m.