Triple
T27687316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elefant |
E698065
|
entity |
| Predicate | mobilityIssue |
P11888
|
FINISHED |
| Object | mechanical unreliability |
—
|
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: mechanical unreliability | Statement: [Elefant, mobilityIssue, mechanical unreliability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mobilityIssue Context triple: [Elefant, mobilityIssue, mechanical unreliability]
-
A.
usesWheelchair
Indicates that an entity relies on or operates a wheelchair for mobility or transportation.
-
B.
wheelchairAccessibility
Indicates whether a place, service, or route is accessible and usable by people who use wheelchairs.
-
C.
mobilityMethod
Indicates the means or method by which an entity moves or is transported from one place to another.
-
D.
mobilityCharacteristic
chosen
Indicates a relationship where an entity is described or classified in terms of its movement or transportation-related properties, such as how, how well, or under what conditions it can move or be moved.
-
E.
supportsMobilityType
Indicates that one entity provides compatibility with, or can function using, a specified type of mobility or movement mode.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63574d2388190839cd1061e3c9074 |
completed | May 2, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:50 p.m.