Triple
T8482505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CASP13 |
E200552
|
entity |
| Predicate | targetsProvidedBy |
P82859
|
FINISHED |
| Object | experimental structural biology laboratories |
—
|
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: experimental structural biology laboratories | Statement: [CASP13, targetsProvidedBy, experimental structural biology laboratories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsProvidedBy Context triple: [CASP13, targetsProvidedBy, experimental structural biology laboratories]
-
A.
intendedTargets
Indicates that an action, message, or object is specifically directed toward or meant to affect particular target entities.
-
B.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
-
C.
targetsSystems
Indicates that an entity is directed at, attacks, or is intended to affect specific systems.
-
D.
targetsShow
Indicates that one entity is the intended audience or focus of a particular show or presentation.
-
E.
aimedAtBy
Indicates that one entity serves as the target or goal toward which another entity directs an action, intention, or focus.
- 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_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. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:12 p.m.