Triple
T7357714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Residence (on selected A380 aircraft) |
E169666
|
entity |
| Predicate | diningService |
P55802
|
FINISHED |
| Object | on-demand à la carte dining |
—
|
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: on-demand à la carte dining | Statement: [The Residence (on selected A380 aircraft), diningService, on-demand à la carte dining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diningService Context triple: [The Residence (on selected A380 aircraft), diningService, on-demand à la carte dining]
-
A.
diningStyle
Indicates the manner or format in which dining is conducted, such as casual, formal, buffet, or family-style.
-
B.
hasDiningFeature
chosen
Indicates that something possesses a specific characteristic, amenity, or attribute related to dining.
-
C.
isDiningDestination
Indicates that a place serves as a destination where people go specifically to eat meals or dine.
-
D.
hasCharacterDining
Indicates that an entity offers or includes dining experiences where guests can eat while interacting with costumed characters.
-
E.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
- 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_69c68a59f2288190877ca15c19b1e822 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26d6d6081909c7272a9ccae0d97 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f02d36108190bcb34a95e6a30bd7 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:06 p.m.