Triple
T8482512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CASP13 |
E200552
|
entity |
| Predicate | resultsPublishedIn |
P309
|
FINISHED |
| Object | scientific literature |
—
|
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: scientific literature | Statement: [CASP13, resultsPublishedIn, scientific literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultsPublishedIn Context triple: [CASP13, resultsPublishedIn, scientific literature]
-
A.
publishedIn
chosen
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
-
B.
reportPublishedIn
Indicates that a specific report appears as content within, or is formally issued through, a particular publication venue (such as a journal, magazine, or report series).
-
C.
appearsInPublication
Indicates that an entity is featured, mentioned, or discussed within a specific publication.
-
D.
publishedDocument
Indicates that an entity has formally issued or made a document publicly available.
-
E.
reportsPublication
Indicates that an entity (such as an author, organization, or system) formally issues or announces a specific publication.
- 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.