Triple
T28537881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matmid Silver |
E722216
|
entity |
| Predicate | benefitsCategory |
P172817
|
FINISHED |
| Object | priority services |
—
|
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: priority services | Statement: [Matmid Silver, benefitsCategory, priority services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitsCategory Context triple: [Matmid Silver, benefitsCategory, priority services]
-
A.
benefitsAre
Indicates that certain advantages, gains, or positive outcomes are possessed by or accrue to a particular entity or group.
-
B.
benefitsArea
Indicates that one entity provides advantages, improvements, or positive effects to a specified area or region.
-
C.
beneficeType
Indicates the specific category or kind of benefice (ecclesiastical office or endowed church position) associated with an entity.
-
D.
benefits
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or action.
-
E.
benefitAppliesTo
Indicates that a particular benefit is applicable to, or valid for, a specified entity or context.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 28, 2026, 3:33 a.m.