Triple
T2958734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Journal Citation Reports |
E79994
|
entity |
| Predicate | coversContentType |
P640
|
FINISHED |
| Object | academic journals |
—
|
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: academic journals | Statement: [Journal Citation Reports, coversContentType, academic journals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversContentType Context triple: [Journal Citation Reports, coversContentType, academic journals]
-
A.
hasContentType
chosen
Indicates that an entity is associated with or classified by a specific type of content.
-
B.
offersContentType
Indicates that one entity provides or makes available content of a specified type to another entity or context.
-
C.
inscriptionContentType
Indicates the type or nature of the content conveyed by an inscription (e.g., its genre, function, or informational category).
-
D.
secondaryContentType
Indicates the type or category of additional, non-primary content associated with an entity or resource.
-
E.
coversSection
Indicates that one entity includes, addresses, or provides content for a particular section of another entity.
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad992c4c7c819084b5bef299255181 |
completed | March 8, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69ad960c5c8881909d679912bd7d78f3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.