Triple
T3797730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoops Hotel |
E91612
|
entity |
| Predicate | amenityAccess |
P5622
|
FINISHED |
| Object | All-Star Sports main pool |
—
|
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: All-Star Sports main pool | Statement: [Hoops Hotel, amenityAccess, All-Star Sports main pool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amenityAccess Context triple: [Hoops Hotel, amenityAccess, All-Star Sports main pool]
-
A.
amenity
chosen
Indicates that one entity provides a useful facility, service, or feature that enhances the convenience or comfort of another entity.
-
B.
amenityLevel
Indicates the degree or quality of facilities, services, or conveniences provided in relation to something.
-
C.
hasPedestrianAccessTo
Indicates that a location or area can be reached or entered safely and directly by people on foot.
-
D.
accessTown
Indicates that an entity has the ability or permission to enter or make use of a particular town.
-
E.
accessibleExit
Indicates that an exit is designed and configured to be usable by people with disabilities, meeting accessibility requirements.
- 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_69aed96354f48190a768966d6bd19b04 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.