Triple
T6459118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis Braille |
E142069
|
entity |
| Predicate | systemUsedBy |
P71108
|
FINISHED |
| Object | blind people |
—
|
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: blind people | Statement: [Louis Braille, systemUsedBy, blind people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemUsedBy Context triple: [Louis Braille, systemUsedBy, blind people]
-
A.
systemType
Indicates the classification or category of a system that an entity belongs to or operates as.
-
B.
usedByOperatingSystems
Indicates that something (such as a component, standard, or feature) is utilized or supported by one or more operating systems.
-
C.
hardwareUsedBy
Indicates that a piece of hardware is utilized or operated by a particular entity (such as a person, system, or organization).
-
D.
hardwareUsed
Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving another entity.
-
E.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
- 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_69c008d2f91c8190a8178767a35e08fc |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069f347f48190a2b22c5b648b17bd |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c068cb3b888190812ed56f2fdd45ed |
completed | March 22, 2026, 10:10 p.m. |
Created at: March 22, 2026, 4:48 p.m.