Triple
T33523260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winnie |
E858566
|
entity |
| Predicate | associatedWithMeaning |
P159298
|
FINISHED |
| Object | blessed peacemaking (via Winifred) |
—
|
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: blessed peacemaking (via Winifred) | Statement: [Winnie, associatedWithMeaning, blessed peacemaking (via Winifred)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMeaning Context triple: [Winnie, associatedWithMeaning, blessed peacemaking (via Winifred)]
-
A.
pairedWithMeaning
chosen
Indicates that one entity is associated with, or linked to, a particular meaning or interpretation of another entity.
-
B.
sharesMeaningWith
Indicates that two expressions convey the same or very similar meaning, even if they differ in form or wording.
-
C.
possibleMeaning
Indicates that something may plausibly represent, signify, or be interpreted as a particular meaning or sense.
-
D.
associatedWithText
Indicates that an entity has a contextual or semantic connection to a specific piece of text.
-
E.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
- 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:39 a.m.