Triple
T20982489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burwash Hall |
E516798
|
entity |
| Predicate | hasDiningService |
P55802
|
FINISHED |
| Object | Victoria University meal plan |
—
|
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: Victoria University meal plan | Statement: [Burwash Hall, hasDiningService, Victoria University meal plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiningService Context triple: [Burwash Hall, hasDiningService, Victoria University meal plan]
-
A.
hasDiningFeature
chosen
Indicates that something possesses a specific characteristic, amenity, or attribute related to dining.
-
B.
hasDiningOptionType
Indicates that an entity offers or is associated with a specific type or category of dining option (e.g., dine-in, takeout, delivery).
-
C.
hasDiningFocus
Indicates that an entity is primarily oriented toward or specialized in dining-related activities, services, or experiences.
-
D.
hasCharacterDining
Indicates that an entity offers or includes dining experiences where guests can eat while interacting with costumed characters.
-
E.
isDiningDestination
Indicates that a place serves as a destination where people go specifically to eat meals or dine.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbe03244819097630333e70c4e88 |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:48 p.m.