Triple
T29107067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CASP14 |
E736788
|
entity |
| Predicate | usesTargetsFrom |
P176733
|
FINISHED |
| Object | X-ray crystallography experiments |
—
|
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: X-ray crystallography experiments | Statement: [CASP14, usesTargetsFrom, X-ray crystallography experiments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTargetsFrom Context triple: [CASP14, usesTargetsFrom, X-ray crystallography experiments]
-
A.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
-
B.
intendedTargets
Indicates that an action, message, or object is specifically directed toward or meant to affect particular target entities.
-
C.
targetsSource
Indicates that something is directed at, aimed toward, or focused on a specified source as its primary origin or object.
-
D.
targetsProvidedBy
Indicates that one entity supplies or makes available specific targets for another entity to use or act upon.
-
E.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
- 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_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e60109648190947a64ca4ce81a3a |
completed | May 3, 2026, 6:06 a.m. |
Created at: April 28, 2026, 11:16 a.m.