Triple
T4566686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron |
E121925
|
entity |
| Predicate | canConfer |
P57745
|
FINISHED |
| Object | social prestige |
—
|
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: social prestige | Statement: [Baron, canConfer, social prestige]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canConfer Context triple: [Baron, canConfer, social prestige]
-
A.
canConcurIn
Indicates that one entity is able or permitted to agree with, coincide with, or participate jointly in the same event, decision, or condition as another entity.
-
B.
canConfirm
Indicates that one entity has the ability or authority to verify the truth, validity, or occurrence of something related to another entity or event.
-
C.
canBeConvenedBy
Indicates that an entity (such as a group, body, or meeting) may be formally brought together or assembled by a specified agent or authority.
-
D.
canPass
Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
-
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. 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd589e35808190aa609bb04b128dbe |
completed | March 20, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69bd5227063c8190973155a875b013a7 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:09 p.m.