Triple
T7999300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monal Restaurant |
E186204
|
entity |
| Predicate | wheelchairAccess |
P36770
|
FINISHED |
| Object | partial |
—
|
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: partial | Statement: [Monal Restaurant, wheelchairAccess, partial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wheelchairAccess Context triple: [Monal Restaurant, wheelchairAccess, partial]
-
A.
hasWheelchairSpace
Indicates that an object, location, or vehicle includes designated space that can accommodate a wheelchair user.
-
B.
usesWheelchair
Indicates that an entity relies on or operates a wheelchair for mobility or transportation.
-
C.
wheelchairTransferRequired
Indicates that a person must be transferred into or out of a wheelchair in order to perform or complete the associated activity or service.
-
D.
isWheelchairAccessibleInPart
chosen
Indicates that an entity is only partially accessible to wheelchair users, with some but not all areas or features meeting accessibility requirements.
-
E.
hasWheelchairLanes
Indicates that a location, route, or facility includes designated lanes or pathways specifically designed for wheelchair use.
- 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c9a12788190a5607a538f4e07c1 |
completed | March 31, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:17 p.m.