Triple
T32306206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mingun Pahtodawgyi |
E825376
|
entity |
| Predicate | haltedBecauseOf |
P126155
|
FINISHED |
| Object | prophecies and resource strain |
—
|
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: prophecies and resource strain | Statement: [Mingun Pahtodawgyi, haltedBecauseOf, prophecies and resource strain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haltedBecauseOf Context triple: [Mingun Pahtodawgyi, haltedBecauseOf, prophecies and resource strain]
-
A.
halted
Indicates that an ongoing process, action, or movement has been stopped or brought to an end.
-
B.
implementationHaltedBy
chosen
Indicates that the progress or continuation of an implementation is stopped or interrupted due to a specified cause or agent.
-
C.
stoppedBy
Indicates that one entity causes another entity to cease moving, operating, or continuing an action.
-
D.
heldFrom
Indicates that an entity is held, possessed, or occupied starting from a specified point in time.
-
E.
stoppedAt
Indicates that an entity has come to a halt or pause at a specific location or point in time.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bd81235081908c0748dfd5db5039 |
completed | May 3, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:45 a.m.