Triple
T4417305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Head (Buffalo) nickel obverse design |
E95004
|
entity |
| Predicate | shapeContext |
P1464
|
FINISHED |
| Object | circular coin face |
—
|
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: circular coin face | Statement: [Indian Head (Buffalo) nickel obverse design, shapeContext, circular coin face]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shapeContext Context triple: [Indian Head (Buffalo) nickel obverse design, shapeContext, circular coin face]
-
A.
shape
chosen
Indicates that one entity has a particular geometric or physical form characterized by the other entity.
-
B.
coreShape
Indicates that one entity serves as the primary or central shape or geometric form of another entity.
-
C.
surfaceFeatureOf
Indicates that one entity is a surface-level characteristic, pattern, or feature belonging to or present on another entity.
-
D.
baseShape
Indicates that one entity serves as the fundamental or underlying shape or form upon which another entity is defined, derived, or constructed.
-
E.
shaped
Indicates that one entity has given form, contour, or structure to another entity or outcome.
- 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3551d5d7481908528c2de0a6fda06 |
completed | March 13, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69b34f5d0c54819085c08533bb58030a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.