Triple
T17358806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Columbia at-large congressional district |
E422014
|
entity |
| Predicate | legallyEstablished |
P41126
|
FINISHED |
| Object | 1970 |
—
|
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: 1970 | Statement: [District of Columbia at-large congressional district, legallyEstablished, 1970]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legallyEstablished Context triple: [District of Columbia at-large congressional district, legallyEstablished, 1970]
-
A.
legalEstablishment
chosen
Indicates that an entity has been formally created, recognized, or brought into existence according to legal rules or procedures.
-
B.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
C.
establishedByStatute
Indicates that something has been formally created, defined, or authorized through a specific law or statute.
-
D.
establishedAs
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
-
E.
usedLegalStatus
Indicates that one entity applies or relies on the legal status or classification of another entity in a given context.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a4a37788190b330b7207aa424b6 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.