Triple
T5241934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leighton Township |
E118362
|
entity |
| Predicate | subdivisionType3 |
P3599
|
FINISHED |
| Object | County |
—
|
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: County | Statement: [Leighton Township, subdivisionType3, County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subdivisionType3 Context triple: [Leighton Township, subdivisionType3, County]
-
A.
hasTypeOfSubdivision
Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
-
B.
subdivisionRank
chosen
Indicates the hierarchical level or type of administrative or territorial subdivision that an entity occupies within a larger organizational or geographic structure.
-
C.
subdividedBy
Indicates that something is divided into smaller parts or sections by another entity or criterion.
-
D.
subdivisionRanks
Indicates the hierarchical ranks or levels into which an entity is further subdivided within a classification or organizational structure.
-
E.
subdivisionISOName
Indicates the standardized ISO-recognized name assigned to a specific administrative subdivision within a country.
- 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_69bd4467db0881909b3b0982df32cc8f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b4c6fa8819099442b1b110e51fb |
completed | March 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.