Triple
T13213231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Seal of the State of Wisconsin |
E314543
|
entity |
| Predicate | hasBottomElement |
P66275
|
FINISHED |
| Object | cornucopia |
—
|
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: cornucopia | Statement: [Great Seal of the State of Wisconsin, hasBottomElement, cornucopia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBottomElement Context triple: [Great Seal of the State of Wisconsin, hasBottomElement, cornucopia]
-
A.
hasBottomSubstrate
Indicates that one entity serves as the underlying or supporting substrate or base layer for another entity.
-
B.
hasBottomness
chosen
Indicates that one entity occupies or represents the lower or bottom position relative to another entity.
-
C.
hasBottomScreenSize
Indicates that an entity has a bottom screen whose size (e.g., dimensions or diagonal measurement) is specified by the related value or object.
-
D.
hasBottomWater
Indicates that an entity contains or is associated with water specifically located at its bottom or lowest part.
-
E.
hasBorderElement
Indicates that one entity includes or is associated with another entity that forms part of its boundary or edge.
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c9f0f148190a0698ef27573c885 |
completed | April 10, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:17 p.m.