Triple
T33015154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martyrs’ Memorial |
E844755
|
entity |
| Predicate | historicalEraCommemorated |
P66853
|
FINISHED |
| Object | 16th 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: 16th century | Statement: [Martyrs’ Memorial, historicalEraCommemorated, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEraCommemorated Context triple: [Martyrs’ Memorial, historicalEraCommemorated, 16th century]
-
A.
periodCommemorated
Indicates that something serves to honor, remember, or mark a specific historical or temporal period.
-
B.
eraCommemorated
chosen
Indicates that a particular era or historical period is honored, remembered, or marked by a commemorative act, object, or event.
-
C.
timeOfEventCommemorated
Indicates the specific time or date at which the event being commemorated originally occurred.
-
D.
eraOfMainCommemoration
Indicates the historical period or era during which the primary commemoration or remembrance of something takes place.
-
E.
hasHistoricSignificanceFor
Indicates that something holds notable historical importance or relevance for a particular entity or group.
- 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_69f3494f3b4081909dccf2af34372a26 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffc605b0648190a7abe9128b0d857a |
completed | May 9, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69ffc5742d80819099f947ece78d5700 |
completed | May 9, 2026, 11:38 p.m. |
Created at: May 1, 2026, 1:23 a.m.