Triple
T125583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto Reports |
E2541
|
entity |
| Predicate | citationForm |
P4468
|
FINISHED |
| Object | volume number Otto page number |
—
|
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: volume number Otto page number | Statement: [Otto Reports, citationForm, volume number Otto page number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: citationForm Context triple: [Otto Reports, citationForm, volume number Otto page number]
-
A.
citation
Indicates that one entity references, quotes, or otherwise acknowledges another entity as a source of information or authority.
-
B.
citationStyle
chosen
Indicates the specific formatting and referencing conventions used to cite sources in a document or publication.
-
C.
publicationType
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
-
D.
legalCitation
Indicates that one legal document, case, or authority formally references or cites another as a source of legal support or precedent.
-
E.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
- 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_69a251b54ea88190b18281669f59b4c0 |
completed | Feb. 28, 2026, 2:23 a.m. |
| NER | Named-entity recognition | batch_69a2573e4e6481908252dfef2e34f46e |
completed | Feb. 28, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69a2564a54948190ba30bee858173b27 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:27 a.m.