Triple
T33025052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alabama Centennial half dollar |
E845016
|
entity |
| Predicate | stateCommemorated |
P4717
|
FINISHED |
| Object | Alabama |
—
|
NE NERFINISHED |
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: Alabama | Statement: [Alabama Centennial half dollar, stateCommemorated, Alabama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateCommemorated Context triple: [Alabama Centennial half dollar, stateCommemorated, Alabama]
-
A.
commemoratedBy
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
-
B.
commemoratedIn
chosen
Indicates that something is honored, remembered, or recognized within a particular work, event, place, or medium.
-
C.
sideCommemorated
Indicates that one side or aspect of an entity is dedicated to honoring or remembering a person, event, or concept.
-
D.
previouslyCommemoratedBy
Indicates that an entity was honored or remembered in the past through a specific commemorative act, object, or event.
-
E.
commemoratedFor
Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: May 1, 2026, 1:23 a.m.