Triple
T8482506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CASP13 |
E200552
|
entity |
| Predicate | assessmentBasedOn |
P51624
|
FINISHED |
| Object | comparison with experimental structures |
—
|
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: comparison with experimental structures | Statement: [CASP13, assessmentBasedOn, comparison with experimental structures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assessmentBasedOn Context triple: [CASP13, assessmentBasedOn, comparison with experimental structures]
-
A.
assessmentBasis
chosen
Indicates the underlying criteria, evidence, or method used as the foundation for making an assessment or evaluation between entities.
-
B.
assessment
Indicates an evaluation or judgment made about an entity’s quality, performance, or characteristics.
-
C.
assessmentMethod
Indicates the method or procedure used to evaluate, measure, or judge something.
-
D.
evaluationBasis
Indicates the criteria, standards, or reference framework used to judge, assess, or measure something in an evaluation process.
-
E.
assessedBy
Indicates that an entity has been evaluated, examined, or judged by another entity (typically an agent or authority).
- 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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53638c48190b742fc51d1b4442a |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:12 p.m.