Triple
T11913724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maha Myat Muni Pagoda |
E283457
|
entity |
| Predicate | hasSecurityPractice |
P101404
|
FINISHED |
| Object | rules on dress code for visitors |
—
|
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: rules on dress code for visitors | Statement: [Maha Myat Muni Pagoda, hasSecurityPractice, rules on dress code for visitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityPractice Context triple: [Maha Myat Muni Pagoda, hasSecurityPractice, rules on dress code for visitors]
-
A.
hasSecurityStandard
Indicates that an entity complies with, follows, or is governed by a specified security standard or framework.
-
B.
hasSecurityArchitecture
Indicates that an entity is associated with or defined by a particular security architecture design or framework.
-
C.
hasSecurityNotion
Indicates that one entity possesses, defines, or is associated with a particular concept or notion of security in relation to another entity or context.
-
D.
hasSecurityRegime
chosen
Indicates that an entity is governed, protected, or controlled by a particular security regime, framework, or set of security rules.
-
E.
hasSecurityPresence
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e52a2bc08190b80cc6ccf5779d7c |
completed | April 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.