Triple
T9522104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shan State |
E229667
|
entity |
| Predicate | hasAutonomyMovements |
P43363
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Shan State, hasAutonomyMovements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAutonomyMovements Context triple: [Shan State, hasAutonomyMovements, true]
-
A.
hasAutonomyMovement
chosen
Indicates that an entity possesses the ability or right to move or operate independently without external control.
-
B.
hasAutonomyOver
Indicates that one entity possesses independent control, decision-making power, or self-governance with respect to another entity or domain.
-
C.
hasAutonomyWithin
Indicates that one entity possesses independent decision-making power or self-governance within the scope, domain, or boundaries defined by another entity.
-
D.
hasLimitedAutonomyIn
Indicates that an entity operates or makes decisions within a domain where its freedom of action is constrained or controlled by another entity or governing context.
-
E.
usesMovement
Indicates that an entity performs or involves some form of movement as part of its action or behavior.
- 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_69ca847870a881909d8d751a7d29da39 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd989788e4819086c235bf37a56b04 |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:59 p.m.