Triple
T31817607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward E. Soda |
E812177
|
entity |
| Predicate | causeOfRecognition |
P128490
|
FINISHED |
| Object | philanthropic contributions |
—
|
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: philanthropic contributions | Statement: [Edward E. Soda, causeOfRecognition, philanthropic contributions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfRecognition Context triple: [Edward E. Soda, causeOfRecognition, philanthropic contributions]
-
A.
publicRecognitionReason
chosen
Indicates the reason or basis for which an entity receives public recognition or acknowledgment.
-
B.
seeksRecognitionOf
Indicates that one entity actively pursues acknowledgment, validation, or formal recognition from another entity.
-
C.
confersRecognition
Indicates that one entity formally acknowledges, honors, or grants recognition to another entity for some quality, status, or achievement.
-
D.
gainedRecognition
Indicates that an entity received acknowledgment, acclaim, or validation from others for its qualities, actions, or achievements.
-
E.
fieldOfRecognition
Indicates the domain, discipline, or area in which an entity is formally acknowledged, honored, or recognized.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 30, 2026, 11:45 p.m.