Triple
T17618299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psychological Review |
E429141
|
entity |
| Predicate | targetContent |
P57060
|
FINISHED |
| Object | broad integrative theoretical papers |
—
|
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: broad integrative theoretical papers | Statement: [Psychological Review, targetContent, broad integrative theoretical papers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetContent Context triple: [Psychological Review, targetContent, broad integrative theoretical papers]
-
A.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
B.
contentIs
Indicates that one entity serves as, or is equivalent to, the content contained within another entity.
-
C.
targetResource
Indicates that one entity designates another entity as the specific resource or object toward which an action, request, or operation is directed.
-
D.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
-
E.
featuredContentType
chosen
Indicates the specific type or category of content that is highlighted or promoted as featured.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d3489dc8190a619c58025dbb250 |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.