Triple
T18252433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Jury Prize |
E437126
|
entity |
| Predicate | hasEvaluationCriteria |
P17142
|
FINISHED |
| Object | direction |
—
|
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: direction | Statement: [Grand Jury Prize, hasEvaluationCriteria, direction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEvaluationCriteria Context triple: [Grand Jury Prize, hasEvaluationCriteria, direction]
-
A.
hasQualityCriterion
Indicates that something is associated with a specific standard or criterion used to judge its quality.
-
B.
hasComparisonCriterion
Indicates that one entity is used as the basis or standard by which another entity is compared or evaluated.
-
C.
evaluationCriteriaInclude
Indicates that certain criteria are part of, or explicitly included in, the set of standards used to evaluate something.
-
D.
evaluationBasis
chosen
Indicates the criteria, standards, or reference framework used to judge, assess, or measure something in an evaluation process.
-
E.
supportsEvaluation
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to be assessed, tested, or evaluated.
- 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd81ea3481909d96b5399f7a32b3 |
completed | April 19, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:33 a.m.