Triple
T8918410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ext3 |
E212349
|
entity |
| Predicate | journalType |
P86396
|
FINISHED |
| Object | metadata journaling (by default) |
—
|
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: metadata journaling (by default) | Statement: [ext3, journalType, metadata journaling (by default)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: journalType Context triple: [ext3, journalType, metadata journaling (by default)]
-
A.
publicationType
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
-
B.
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.
-
C.
magazineType
Indicates the specific category or genre to which a magazine belongs.
-
D.
journalSupport
Indicates that one entity provides support, resources, or assistance to another in the context of a journal or journal-related activities.
-
E.
manuscriptType
Indicates the specific category or kind of manuscript associated with an entity (e.g., draft, final version, annotated copy).
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66120eb08190913ab6c42f26ffb8 |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc600a59708190ae426044bbcd7929 |
completed | April 1, 2026, midnight |
Created at: March 30, 2026, 6:56 p.m.