Triple
T27427485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pa-O people |
E690529
|
entity |
| Predicate | selfAdministeredArea |
P106708
|
FINISHED |
| Object | Pa-O Self-Administered Zone |
—
|
NE NERFINISHED |
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: Pa-O Self-Administered Zone | Statement: [Pa-O people, selfAdministeredArea, Pa-O Self-Administered Zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selfAdministeredArea Context triple: [Pa-O people, selfAdministeredArea, Pa-O Self-Administered Zone]
-
A.
hasAdministrativeArea
Indicates that one entity serves as the governing or jurisdictional area responsible for administering another entity.
-
B.
hasAutonomousArea
chosen
Indicates that an entity possesses or contains a geographically or administratively distinct area that has a degree of self-governance or autonomy.
-
C.
hasAreaNumber
Indicates that an entity is associated with a specific area identified by a numerical code.
-
D.
regulatesArea
Indicates that one entity exercises control or governance over the spatial extent, scope, or domain of another entity.
-
E.
hasHealthArea
Indicates that an entity is associated with, or falls within the scope of, a particular health-related domain or area of concern.
- 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_69ef52003fb48190b0f1295246182a86 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62d553c1c81909aace359027f4019 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:41 p.m.