Triple
T26311604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahmad |
E661839
|
entity |
| Predicate | providesPerspectiveIn |
P60524
|
FINISHED |
| Object | Soul Food |
—
|
NE NERFINISHED |
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: Soul Food | Statement: [Ahmad, providesPerspectiveIn, Soul Food]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesPerspectiveIn Context triple: [Ahmad, providesPerspectiveIn, Soul Food]
-
A.
exploresPerspectiveOf
Indicates that one entity examines, investigates, or considers the viewpoint, stance, or outlook associated with another entity.
-
B.
perspectiveOf
Indicates that something is expressed, depicted, or understood from the viewpoint or standpoint of a particular entity.
-
C.
knownForPerspective
Indicates that an entity is recognized or notable for a particular viewpoint, angle, or way of seeing or interpreting something.
-
D.
useOfPerspective
Indicates that one entity adopts or applies a particular visual, narrative, or conceptual viewpoint in relation to another entity or context.
-
E.
introducesPerspective
chosen
Indicates that one entity presents or brings in a particular viewpoint, angle, or way of understanding regarding another entity or situation.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 26, 2026, 10:22 p.m.