Triple
T17485810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PsycARTICLES |
E425774
|
entity |
| Predicate | contentCoverage |
P41428
|
FINISHED |
| Object | psychology 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: psychology journals | Statement: [PsycARTICLES, contentCoverage, psychology journals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentCoverage Context triple: [PsycARTICLES, contentCoverage, psychology journals]
-
A.
contentIs
Indicates that one entity serves as, or is equivalent to, the content contained within another entity.
-
B.
contentLevel
Indicates the degree or intensity of substance, complexity, or richness present in the associated content.
-
C.
coversSection
chosen
Indicates that one entity includes, addresses, or provides content for a particular section of another entity.
-
D.
stageCoverage
Indicates that one entity provides or has coverage, representation, or support for another within a particular stage or phase of a process or workflow.
-
E.
contentUsage
Indicates how a piece of content is intended to be used, accessed, or consumed within a given context or system.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451d1f4708190b7c4d61326a2c4a4 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.