Triple
T16760460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Burma |
E407327
|
entity |
| Predicate | hasRecipientNationality |
P59748
|
FINISHED |
| Object | Burmese |
—
|
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: Burmese | Statement: [Order of Burma, hasRecipientNationality, Burmese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecipientNationality Context triple: [Order of Burma, hasRecipientNationality, Burmese]
-
A.
recipientNationality
chosen
Indicates that the recipient in a relationship or transaction has a specified national affiliation or citizenship.
-
B.
hasParticipantNationality
Indicates that a participant in an event, activity, or relation has a specific nationality.
-
C.
appliesToPersonNationality
Indicates that something is relevant or applicable specifically to a person’s nationality.
-
D.
hasNationalityRecord
Indicates that there exists an official record documenting an entity's nationality or national affiliation.
-
E.
bearerNationality
Indicates that one entity is the country or nationality associated with the bearer of another entity, such as a document or credential.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3abec638c81909d71ff452a4123c9 |
completed | April 18, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.