Triple
T3392491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington, D.C. |
E71451
|
entity |
| Predicate | federalDistrictStatus |
P23390
|
FINISHED |
| Object | not part of any U.S. state |
—
|
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: not part of any U.S. state | Statement: [Washington, D.C., federalDistrictStatus, not part of any U.S. state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: federalDistrictStatus Context triple: [Washington, D.C., federalDistrictStatus, not part of any U.S. state]
-
A.
federalStatus
chosen
Indicates that an entity holds a particular legal or administrative status under federal (national) authority or jurisdiction.
-
B.
includesFederalDistrict
Indicates that one administrative or geographic entity contains or encompasses a federal district within its boundaries.
-
C.
federalDistrictSince
Indicates that an entity has held the status of a federal district starting from a specified point in time.
-
D.
federalDistrictComponent
Indicates that one administrative or territorial unit is a constituent part of a federal district within a federal system.
-
E.
federalDistrictNumber
Indicates the specific numbered federal electoral or administrative district associated with an entity.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb851e57c8190983cadcedc58db50 |
completed | March 8, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.