Triple
T26490925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Official Report |
E669152
|
entity |
| Predicate | isTypicallyPublishedIn |
P309
|
FINISHED |
| Object | print format |
—
|
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: print format | Statement: [Official Report, isTypicallyPublishedIn, print format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTypicallyPublishedIn Context triple: [Official Report, isTypicallyPublishedIn, print format]
-
A.
publishedIn
chosen
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.
-
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.
intendedPublication
Indicates that one entity is planned or designated to be published in or through another entity (such as a venue, medium, or edition).
-
D.
isPublishedWith
Indicates that an entity is released or made publicly available together with another specified entity, typically as part of the same publication or release event.
-
E.
fieldOfPublication
Indicates the academic or topical area in which a work is published.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:04 a.m.