Triple
T17142020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roy Nachum |
E415990
|
entity |
| Predicate | usesMaterialOrTechnique |
P1272
|
FINISHED |
| Object | Braille |
—
|
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: Braille | Statement: [Roy Nachum, usesMaterialOrTechnique, Braille]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMaterialOrTechnique Context triple: [Roy Nachum, usesMaterialOrTechnique, Braille]
-
A.
usesMaterialBy
Indicates that one entity makes use of or employs a material that is provided, specified, or created by another entity.
-
B.
appliedToMaterial
Indicates that an action, process, or treatment is performed on or directed toward a specific material.
-
C.
usedByTechnique
Indicates that a particular technique makes use of or employs the referenced entity as part of its method or process.
-
D.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
E.
associatedWithMaterial
Indicates a relationship where something is linked or connected to a particular material, typically as its substance, component, or relevant physical medium.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2d5de10819090cbd65661b018d3 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.