Triple
T30770328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wa Self-Administered Division |
E783504
|
entity |
| Predicate | isMinorityRegion |
P152140
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Wa Self-Administered Division, isMinorityRegion, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMinorityRegion Context triple: [Wa Self-Administered Division, isMinorityRegion, yes]
-
A.
isMinorityTownIn
Indicates that a town is located within a larger region or jurisdiction where it is classified as a minority community.
-
B.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with another entity.
-
C.
isMajorRegionFor
Indicates that a region serves as a primary or significant area associated with a particular entity, activity, or phenomenon.
-
D.
hasMinorityAutonomyContext
chosen
Indicates that the situation involves a context in which a minority group possesses some degree of self-governance, special rights, or autonomous decision-making authority within a larger political or social framework.
-
E.
hasMinorityIn
Indicates that one entity holds a non-controlling, minority ownership or stake in another entity.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68fc0ca388190a0c762deb514748d |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:40 p.m.