Triple
T34462470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seat of Government Clause |
E884681
|
entity |
| Predicate | limitsDistrictSizeTo |
P73084
|
FINISHED |
| Object | ten miles square |
—
|
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: ten miles square | Statement: [Seat of Government Clause, limitsDistrictSizeTo, ten miles square]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitsDistrictSizeTo Context triple: [Seat of Government Clause, limitsDistrictSizeTo, ten miles square]
-
A.
districtSize
Indicates the total physical area or extent of a district.
-
B.
isSmallDistrict
Indicates that a district is classified as small, typically based on its limited size, population, or administrative scope.
-
C.
minimumSeatsPerDistrict
Indicates the required minimum number of seats that must be allocated to each district.
-
D.
numberOfDistricts
Indicates the total count of districts associated with a given entity or area.
-
E.
dimensionRestriction
chosen
Indicates a constraint or limit imposed on the size, extent, or number of dimensions associated with an entity 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_69f349c73a94819094dfcf50d00620b8 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2 a.m.