Triple
T8538899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sam Davis Memorial |
E202145
|
entity |
| Predicate | hasHistoricalPeriodCommemorated |
P5669
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Sam Davis Memorial, hasHistoricalPeriodCommemorated, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalPeriodCommemorated Context triple: [Sam Davis Memorial, hasHistoricalPeriodCommemorated, 19th century]
-
A.
commemoratedSince
Indicates that a commemoration of one entity for another has been in effect starting from a specific point in time.
-
B.
periodCommemorated
chosen
Indicates that something serves to honor, remember, or mark a specific historical or temporal period.
-
C.
previouslyCommemoratedBy
Indicates that an entity was honored or remembered in the past through a specific commemorative act, object, or event.
-
D.
hasCommemorationFunction
Indicates that something serves the role or purpose of commemorating an event, person, group, or concept.
-
E.
hasHistoricalSignificance
Indicates that something possesses notable importance or influence within a historical context or period.
- 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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6a7441c8190980c3516073422fe |
completed | March 31, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:18 p.m.