Triple
T9340583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rorschach |
E224753
|
entity |
| Predicate | journalUsedFor |
P87612
|
FINISHED |
| Object | recording his investigations |
—
|
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: recording his investigations | Statement: [Rorschach, journalUsedFor, recording his investigations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: journalUsedFor Context triple: [Rorschach, journalUsedFor, recording his investigations]
-
A.
journalSupport
Indicates that one entity provides support, resources, or assistance to another in the context of a journal or journal-related activities.
-
B.
journalType
Indicates the specific category or format of a journal associated with an entity.
-
C.
isJournalOf
Indicates that one entity serves as the journal in which the other entity (such as an article or work) is published or to which it belongs.
-
D.
publishedIn
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.
-
E.
publishingVenue
Indicates the venue (such as a journal, conference, or publisher) where a work is formally published.
- 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_69ca84286fcc81909f6e7fd7a7e862a2 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4bae2e2481909effc2dc89a642c5 |
completed | April 1, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69cc7a66aef08190b8d668cff5b04f5f |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:40 p.m.