Triple
T32306691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prome District (historical) |
E825389
|
entity |
| Predicate | containedTownship |
P22464
|
FINISHED |
| Object | Prome 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: Prome Township | Statement: [Prome District (historical), containedTownship, Prome Township]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containedTownship Context triple: [Prome District (historical), containedTownship, Prome Township]
-
A.
hasTownship
chosen
Indicates that one administrative area or jurisdiction includes or is associated with a specific township.
-
B.
regionContainsTowns
Indicates that a geographic region includes or encompasses one or more towns within its boundaries.
-
C.
containsSuburbanAreaOf
Indicates that one geographic region includes within its boundaries a suburban area belonging to or associated with another region.
-
D.
isInteriorTownOf
Indicates that one town is located within the interior region of, and is administratively or geographically associated with, a larger area or jurisdiction.
-
E.
involvedTown
Indicates that a town participates in, is associated with, or is affected by a particular event, activity, or relationship.
- 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_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
Created at: May 1, 2026, 12:45 a.m.