Triple
T24755516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riverside Heights |
E619273
|
entity |
| Predicate | hasParentMunicipalityType |
P108590
|
FINISHED |
| Object | township |
—
|
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: township | Statement: [Riverside Heights, hasParentMunicipalityType, township]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentMunicipalityType Context triple: [Riverside Heights, hasParentMunicipalityType, township]
-
A.
hasMunicipalityType
Indicates that an administrative unit is classified as having a specific type or category of municipality (e.g., city, town, village).
-
B.
isPartOfMunicipalityType
chosen
Indicates that one administrative unit or area belongs to, or is classified under, a specific type or category of municipality.
-
C.
hasParentSocietyType
Indicates that an entity is associated with, or belongs to, a broader parent society categorized by a specific type.
-
D.
hasParentAgencyType
Indicates that an agency is associated with or falls under a parent agency of a specified type.
-
E.
typeOfMunicipalRelationship
Indicates a formal type or category of administrative or cooperative relationship that exists between municipalities.
- 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 4:26 a.m.