Triple
T19632087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grain Elevators series |
E471294
|
entity |
| Predicate | intendedViewingMode |
P30377
|
FINISHED |
| Object | comparative analysis of forms |
—
|
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: comparative analysis of forms | Statement: [Grain Elevators series, intendedViewingMode, comparative analysis of forms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedViewingMode Context triple: [Grain Elevators series, intendedViewingMode, comparative analysis of forms]
-
A.
intendedViewerExperience
Indicates the type or quality of experience that a piece of content is designed or expected to provide to its viewers.
-
B.
viewingIs
Indicates that one entity is engaged in the act or state of viewing, observing, or watching another entity.
-
C.
displayMode
chosen
Indicates how content or information is visually presented or arranged to the user.
-
D.
intendedViewingDistance
Indicates the distance at which something is meant or designed to be viewed or observed.
-
E.
viewingMethod
Indicates the manner or technique by which something is observed, displayed, or visually accessed.
- 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.