Triple
T31120215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montana congressional delegation |
E793200
|
entity |
| Predicate | startPointOfCurrentTwoHouseDistrictStructure |
P389
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [Montana congressional delegation, startPointOfCurrentTwoHouseDistrictStructure, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startPointOfCurrentTwoHouseDistrictStructure Context triple: [Montana congressional delegation, startPointOfCurrentTwoHouseDistrictStructure, 2023]
-
A.
startPointAsUrbanDistrict
Indicates that the starting point of something (e.g., a route, event, or process) is located within an urban district.
-
B.
startPointAsMunicipalBorough
Indicates that an entity begins or originates within the jurisdiction or boundaries of a specific municipal borough.
-
C.
startPointLocatedIn
Indicates that the starting point of something is geographically or spatially located within a specified area or region.
-
D.
endPointDistrict
Indicates the district in which a path, route, or connection terminates.
-
E.
startPoint
chosen
Indicates the initial location or position from which an object, path, or action begins.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
Created at: April 29, 2026, 9:04 p.m.