Triple
T23265157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JMB Crystal |
E588125
|
entity |
| Predicate | statusGroup |
P151597
|
FINISHED |
| Object | JAL FLY ON Program tiers |
—
|
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: JAL FLY ON Program tiers | Statement: [JMB Crystal, statusGroup, JAL FLY ON Program tiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusGroup Context triple: [JMB Crystal, statusGroup, JAL FLY ON Program tiers]
-
A.
statusSymbol
Indicates that something serves as a marker or representation of an entity’s social, economic, or cultural standing relative to others.
-
B.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
-
C.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
-
D.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
E.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
- F. None of above. chosen
Provenance (4 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f194cc3b908190aaefd036aa2b52b5 |
completed | April 29, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:29 p.m.