Triple
T35563983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DC Defenders |
E1027716
|
entity |
| Predicate | homeStateOrDistrict |
P59559
|
FINISHED |
| Object | District of Columbia |
—
|
NE NERFINISHED |
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: District of Columbia | Statement: [DC Defenders, homeStateOrDistrict, District of Columbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStateOrDistrict Context triple: [DC Defenders, homeStateOrDistrict, District of Columbia]
-
A.
homeState
Indicates that a person or organization has their primary residence, registration, or official base in a particular state.
-
B.
districtOfState
Indicates that a district is an administrative subdivision belonging to, and located within, a particular state.
-
C.
representedState
Indicates that one entity serves as a representation or depiction of the state or condition of another entity.
-
D.
homeStateFlag
Indicates that a particular flag is officially recognized as the state flag of the referenced home state.
-
E.
primaryStateAffiliation
chosen
Indicates the main governmental or regional jurisdiction with which an entity is officially associated or aligned.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:04 p.m.