Triple
T2082347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spaceship Earth |
E45270
|
entity |
| Predicate | wheelchairTransferRequired |
P35684
|
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: [Spaceship Earth, wheelchairTransferRequired, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wheelchairTransferRequired Context triple: [Spaceship Earth, wheelchairTransferRequired, yes]
-
A.
hasWheelchairLanes
Indicates that a location, route, or facility includes designated lanes or pathways specifically designed for wheelchair use.
-
B.
isDifficultToAccessBecauseOf
Indicates that something is hard to reach, obtain, or use due to a specified obstacle, condition, or circumstance.
-
C.
hasStepFreeAccess
Indicates that a location, facility, or route can be accessed without using stairs, typically via ramps, lifts, or level entrances.
-
D.
wheelchairDivision
Indicates that an entity participates in or is associated with a competition, league, or category specifically designated for wheelchair users.
-
E.
wheelchairEventsIncluded
Indicates that the specified events explicitly include or accommodate the use of wheelchairs.
- 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba5097ac8190a723a8af2982238c |
completed | March 7, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69abb7b298a48190b4bdf7c9800b058d |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb94ec400819097596732aabed854 |
completed | March 7, 2026, 5:36 a.m. |
Created at: March 4, 2026, 7:41 p.m.