Triple
T8415982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Effie Awards |
E198730
|
entity |
| Predicate | evaluationInvolves |
P1256
|
FINISHED |
| Object | case study submissions |
—
|
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: case study submissions | Statement: [Effie Awards, evaluationInvolves, case study submissions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evaluationInvolves Context triple: [Effie Awards, evaluationInvolves, case study submissions]
-
A.
supportsEvaluation
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to be assessed, tested, or evaluated.
-
B.
evaluationRole
Indicates the role or capacity in which an entity participates in an evaluation or assessment process.
-
C.
evaluationUse
Indicates that something is used as a basis, tool, or resource for evaluating or assessing something else.
-
D.
evaluationBasis
Indicates the criteria, standards, or reference framework used to judge, assess, or measure something in an evaluation process.
-
E.
involves
chosen
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb84c5121081908efa3eca25406d3a |
completed | March 31, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.