Triple
T29925792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martyrs’ Day (Myanmar) |
E760076
|
entity |
| Predicate | mainLocationOfObservance |
P54305
|
FINISHED |
| Object | Yangon |
—
|
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: Yangon | Statement: [Martyrs’ Day (Myanmar), mainLocationOfObservance, Yangon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainLocationOfObservance Context triple: [Martyrs’ Day (Myanmar), mainLocationOfObservance, Yangon]
-
A.
traditionalLocationOfObservance
Indicates the place where an event, practice, or observance has been customarily or historically carried out.
-
B.
locationOfObservance
chosen
Indicates the place where an event, ceremony, or observance occurs or is carried out.
-
C.
liturgicalLocation
Indicates the place or setting where a liturgical act, ritual, or religious service occurs.
-
D.
isMostFamouslyObservedIn
Indicates that something is best known or primarily recognized for being observed or occurring in a particular place, context, or setting.
-
E.
ecclesiasticalCenter
Indicates that a place functions as a primary religious or church administrative hub for a surrounding area or community.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 6:16 p.m.