Triple
T3507322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salzmann |
E74106
|
entity |
| Predicate | likelyRefersTo |
P24766
|
FINISHED |
| Object | person working with salt |
—
|
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: person working with salt | Statement: [Salzmann, likelyRefersTo, person working with salt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyRefersTo Context triple: [Salzmann, likelyRefersTo, person working with salt]
-
A.
refersSpecificallyTo
Indicates that one entity makes an explicit, precise reference to another particular entity, distinguishing it from more general or ambiguous references.
-
B.
refersToPerson
chosen
Indicates that one entity is making reference to, mentioning, or pointing specifically to a particular person.
-
C.
refersToRole
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
-
D.
refersToAspect
Indicates that one entity specifically references or points to a particular aspect, feature, or component of another entity.
-
E.
canRefer
Indicates that one entity has the ability or permission to mention, point to, or direct attention to 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc0b635c81909bc95ba2562d8f94 |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0e770481908528fa35eda53003 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.