Triple
T32404443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MD-03 |
E828037
|
entity |
| Predicate | isNumberedDistrictWithinState |
P138276
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [MD-03, isNumberedDistrictWithinState, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNumberedDistrictWithinState Context triple: [MD-03, isNumberedDistrictWithinState, 3]
-
A.
isNumberedWithinState
chosen
Indicates that an entity has an assigned number that is unique or valid only within the context or boundaries of a particular state.
-
B.
federalDistrictNumber
Indicates the specific numbered federal electoral or administrative district associated with an entity.
-
C.
hasStateOrDistrict
Indicates that an entity is associated with, located in, or belongs to a particular state or district.
-
D.
isSingleDistrictFor
Indicates that one district uniquely and exclusively serves or applies to a given entity, with no other districts sharing that role.
-
E.
isKeyDistrictOf
Indicates that a district holds strategic, political, or administrative importance within a larger region, organization, or system.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2451e108190a73ccfdc99203d55 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:53 a.m.