Triple
T22052463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ocean between Montreal and Halifax |
E544917
|
entity |
| Predicate | hasOnboardCatering |
P142841
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [The Ocean between Montreal and Halifax, hasOnboardCatering, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnboardCatering Context triple: [The Ocean between Montreal and Halifax, hasOnboardCatering, yes]
-
A.
hasCateringServices
chosen
Indicates that an entity provides or offers catering services, such as preparing and supplying food and beverages for events or clients.
-
B.
cateringIncludes
Indicates that a catering service or arrangement encompasses or provides the specified item, service, or component as part of its offering.
-
C.
hasSpecialMeal
Indicates that an entity provides, is assigned, or is associated with a designated special meal option.
-
D.
hasDiningOptionType
Indicates that an entity offers or is associated with a specific type or category of dining option (e.g., dine-in, takeout, delivery).
-
E.
offersBuffet
Indicates that one entity provides a buffet-style service or meal option to 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1285513fc8190b691e1f57085956f |
completed | April 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:26 p.m.