Triple
T31508893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pa-O Self-Administered Zone |
E803890
|
entity |
| Predicate | composedOfTownship |
P22464
|
FINISHED |
| Object | Hopong Township |
—
|
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: Hopong Township | Statement: [Pa-O Self-Administered Zone, composedOfTownship, Hopong Township]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composedOfTownship Context triple: [Pa-O Self-Administered Zone, composedOfTownship, Hopong Township]
-
A.
hasTownship
chosen
Indicates that one administrative area or jurisdiction includes or is associated with a specific township.
-
B.
fromTown
Indicates that one entity originates from, or is associated as being from, a particular town represented by the other entity.
-
C.
formedMunicipalityWith
Indicates that two or more entities combined or were merged to create a single municipality.
-
D.
servesTownship
Indicates that an entity provides official services or administrative functions to a particular township.
-
E.
relationshipToTownship
Indicates the specific type of relationship or association that an entity has with a particular township.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 30, 2026, 9:49 p.m.