Triple
T19632070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grain Elevators series |
E471294
|
entity |
| Predicate | typicalPrintFormat |
P100095
|
FINISHED |
| Object | grid of multiple images |
—
|
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: grid of multiple images | Statement: [Grain Elevators series, typicalPrintFormat, grid of multiple images]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPrintFormat Context triple: [Grain Elevators series, typicalPrintFormat, grid of multiple images]
-
A.
typicalFinalFormat
Indicates that something represents the usual or standard structure or arrangement in which an item, document, or data is ultimately presented or delivered.
-
B.
isTypicallyPrinted
Indicates that something is commonly or usually produced in printed form rather than in another medium.
-
C.
printedInFormat
chosen
Indicates that something has been produced or output using a specified printing format or layout.
-
D.
projectionPrintType
Indicates the method or format by which a projection is printed or rendered (e.g., type or style of the projection output).
-
E.
printType
Indicates the method or format by which something is printed or physically reproduced.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641036ee881909fdd8170fe4cdac9 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.