Triple
T4435480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bessarion |
E95637
|
entity |
| Predicate | hasTactilePlatformEdgeStrips |
P51959
|
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: [Bessarion, hasTactilePlatformEdgeStrips, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTactilePlatformEdgeStrips Context triple: [Bessarion, hasTactilePlatformEdgeStrips, yes]
-
A.
hasSidePlatforms
Indicates that something is equipped with platforms located on its sides, typically for access, support, or operation.
-
B.
hasIOPads
Indicates that an entity is equipped with or associated with input/output pads used for electrical or signal connections.
-
C.
hasOnboardLEDs
Indicates that one entity is equipped with built-in LED lights as part of its hardware.
-
D.
flankedByStripes
Indicates that an entity is positioned between or bordered on both sides by stripe-like elements.
-
E.
hasFloorMarkings
chosen
Indicates that an entity features visible markings or lines on its floor surface, typically used for guidance, organization, or safety.
- 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_69b3453ea2b48190a26f154b3b8fece5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35589f8608190b0820d36beaacf44 |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f6078cc8190831b89f404198cc5 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:31 p.m.