Triple
T3200488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garden Wing |
E67036
|
entity |
| Predicate | hasCheckInLocation |
P46096
|
FINISHED |
| Object | main lobby of Disney's Contemporary Resort |
—
|
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: main lobby of Disney's Contemporary Resort | Statement: [Garden Wing, hasCheckInLocation, main lobby of Disney's Contemporary Resort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCheckInLocation Context triple: [Garden Wing, hasCheckInLocation, main lobby of Disney's Contemporary Resort]
-
A.
hasCheckInSystem
Indicates that an entity uses or is equipped with a system for registering or recording check-ins.
-
B.
hasCheckInBuilding
Indicates that an entity has performed a check-in event within a specified building.
-
C.
hasCheckOutTime
Indicates the specific time at which an entity is required or scheduled to check out or depart.
-
D.
hasMeetingLocation
Indicates that an entity (such as a meeting or event) takes place at or is associated with a specific location.
-
E.
hasCheckInCategory
Indicates that an entity is associated with a specific category or type of check-in event.
- 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada9aedef08190824bdf508f85f06f |
completed | March 8, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69ad9e05e4f48190adbe4366cdba2349 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:07 p.m.