Triple
T7586116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jefferson nickel |
E179615
|
entity |
| Predicate | wartimeComposition |
P78000
|
FINISHED |
| Object | 56% copper |
—
|
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: 56% copper | Statement: [Jefferson nickel, wartimeComposition, 56% copper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wartimeComposition Context triple: [Jefferson nickel, wartimeComposition, 56% copper]
-
A.
wartimeUse
Indicates that something is used or employed during a period of war or armed conflict.
-
B.
wartimeControl
Indicates that one entity exercises authoritative command or governance over another entity specifically during a period of armed conflict or war.
-
C.
wartimeGain
Indicates that an entity acquires benefits, resources, or advantages specifically as a result of wartime conditions or activities.
-
D.
wartimeContext
Indicates that the related entities, events, or actions occur within, are shaped by, or are directly connected to a period of armed conflict or war.
-
E.
wartimeParent
Indicates that one entity is the parent of another in the specific context of a wartime situation or period.
- F. None of above. chosen
Provenance (4 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_69c69f335248819093c1006f30513708 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f995c8a8819089817bd679640017 |
completed | March 27, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:52 p.m.