Triple
T7069509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winston, North Carolina |
E164648
|
entity |
| Predicate | municipalType |
P10835
|
FINISHED |
| Object | town |
—
|
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: town | Statement: [Winston, North Carolina, municipalType, town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalType Context triple: [Winston, North Carolina, municipalType, town]
-
A.
municipalWardType
Indicates the specific category or classification of a municipal ward within a local government or administrative structure.
-
B.
hasMunicipalityType
chosen
Indicates that an administrative unit is classified as having a specific type or category of municipality (e.g., city, town, village).
-
C.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
-
D.
municipality
Indicates that one entity is a municipality (a local administrative unit) in which the other entity is located or which it governs.
-
E.
municipalOwnership
Indicates that an entity is owned, controlled, or held as property by a municipal (city or local) government.
- 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_69c6887b96548190a8a9b3ac8adf4119 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4aa82108190bacd5584c1c78999 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:39 p.m.