Triple
T34733415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Min Razagyi |
E1001273
|
entity |
| Predicate | notablePortInRealm |
P6498
|
FINISHED |
| Object | Mrauk U |
E1181604
|
NE 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: Mrauk U | Statement: [Min Razagyi, notablePortInRealm, Mrauk U]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePortInRealm Context triple: [Min Razagyi, notablePortInRealm, Mrauk U]
-
A.
notablePort
chosen
Indicates that a location is recognized as an important or prominent port, typically due to its significance in trade, transport, or maritime activity.
-
B.
notableRealm
Indicates that an entity is notably associated with, active in, or recognized within a particular domain, field, or sphere of activity.
-
C.
notableGate
Indicates that a gate is recognized as significant, prominent, or noteworthy in some context.
-
D.
notableKey
Indicates that the referenced key is of particular importance or prominence compared to other keys in the same context.
-
E.
notableEnclave
Indicates that one place is a distinct, noteworthy enclave located within or surrounded by another area or community.
- F. None of above.
Provenance (4 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_69f76daf739881909ed3554f98a2b433 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37c6190de08190a224ead90fd1b4e5 |
completed | June 21, 2026, 11:08 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.