Triple
T3856113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Home Run Hotel |
E90017
|
entity |
| Predicate | hasAmenityAccess |
P1017
|
FINISHED |
| Object | Disney bus transportation |
—
|
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: Disney bus transportation | Statement: [Home Run Hotel, hasAmenityAccess, Disney bus transportation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAmenityAccess Context triple: [Home Run Hotel, hasAmenityAccess, Disney bus transportation]
-
A.
hasVehicleAccess
Indicates that an entity is permitted to use or enter a particular vehicle.
-
B.
amenityLevel
Indicates the degree or quality of facilities, services, or conveniences provided in relation to something.
-
C.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
D.
accessibleOn
Indicates that one entity can be reached, used, or obtained through another entity (such as a platform, device, or medium).
-
E.
hasAccessTo
chosen
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
- 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_69aed95b3c088190a8f85d19e6070599 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec07d45081909b8f3e35eb710f4c |
completed | March 9, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69aee752c8a48190a670f73ed0bf1e61 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.