Triple
T13018972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kota Pahlawan |
E322625
|
entity |
| Predicate | hasParticularDateOfCommemoration |
P865
|
FINISHED |
| Object | 10 November |
—
|
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: 10 November | Statement: [Kota Pahlawan, hasParticularDateOfCommemoration, 10 November]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParticularDateOfCommemoration Context triple: [Kota Pahlawan, hasParticularDateOfCommemoration, 10 November]
-
A.
commemorationDate
Indicates the date on which an event, person, or occasion is formally remembered or honored.
-
B.
commemoratedOn
chosen
Indicates that something is remembered, honored, or celebrated on a specific date or occasion.
-
C.
commemoratesEventOn
Indicates that one entity marks, honors, or observes a specific event on a particular date or occasion.
-
D.
periodCommemorated
Indicates that something serves to honor, remember, or mark a specific historical or temporal period.
-
E.
formerlyCommemoratedOn
Indicates that an entity was previously commemorated or observed on a particular date, but is no longer commemorated on that date.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ece22908190a0941e23df7c774d |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:51 p.m.