Triple
T29107065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CASP14 |
E736788
|
entity |
| Predicate | hasEvaluationType |
P166340
|
FINISHED |
| Object | blind prediction assessment |
—
|
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: blind prediction assessment | Statement: [CASP14, hasEvaluationType, blind prediction assessment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEvaluationType Context triple: [CASP14, hasEvaluationType, blind prediction assessment]
-
A.
supportsEvaluation
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to be assessed, tested, or evaluated.
-
B.
hasAnalysisType
Indicates that one entity is associated with, or characterized by, a specific type or category of analysis applied to it.
-
C.
taskTypesEvaluated
Indicates that specific types or categories of tasks have been examined or assessed.
-
D.
hasScoreType
Indicates that an entity is associated with a particular type or category of score.
-
E.
hasGradeType
Indicates that an entity is associated with a particular category or type of grade (e.g., letter grade, pass/fail, percentage).
- F. None of above. chosen
Provenance (4 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661bb81b481909690f8617a84cb19 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 11:16 a.m.