Triple
T11975147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Salathé |
E285020
|
entity |
| Predicate | usedSkill |
P96902
|
FINISHED |
| Object | metalworking |
—
|
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: metalworking | Statement: [John Salathé, usedSkill, metalworking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedSkill Context triple: [John Salathé, usedSkill, metalworking]
-
A.
hasEponymousSkill
Indicates that an entity possesses a skill that is named after a particular person or entity.
-
B.
skilledIn
Indicates that an entity possesses ability, expertise, or proficiency in performing or using another entity (such as a task, tool, or domain).
-
C.
kills
Indicates that one entity causes the death of another entity, ending its life.
-
D.
killsByProxy
Indicates that one entity causes the death of another entity indirectly through an intermediary or agent rather than committing the act personally.
-
E.
indicatesSkill
chosen
Indicates a relationship where one entity possesses, demonstrates, or is associated with a particular skill represented by another entity.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903926690819090e7ce982f103457 |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:46 p.m.