Triple
T34394753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singapore Airlines passengers |
E882799
|
entity |
| Predicate | flyOn |
P179157
|
FINISHED |
| Object | Singapore Airlines Economy Class |
—
|
NE NERFINISHED |
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: Singapore Airlines Economy Class | Statement: [Singapore Airlines passengers, flyOn, Singapore Airlines Economy Class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flyOn Context triple: [Singapore Airlines passengers, flyOn, Singapore Airlines Economy Class]
-
A.
fliesWith
Indicates that one entity travels through the air in the company of, or using the same aircraft or flying means as, another entity.
-
B.
flightOver
Indicates that one entity moves through the air above or across another entity or area.
-
C.
fliesFlag
Indicates that one entity displays or hoists the flag of another entity, symbolically representing affiliation, identity, or allegiance.
-
D.
flybyOf
Indicates that one entity passes close to another in space without stopping, typically as part of an observational or transit maneuver.
-
E.
flightStyle
Indicates the characteristic manner or pattern in which an entity performs or exhibits flight.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71c33edac8190a59f6ff19b265fc5 |
completed | May 3, 2026, 9:58 a.m. |
Created at: May 1, 2026, 1:59 a.m.