Triple
T26822829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murder on K Street |
E675296
|
entity |
| Predicate | setInCapital |
P161510
|
FINISHED |
| Object | Washington, D.C. |
—
|
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: Washington, D.C. | Statement: [Murder on K Street, setInCapital, Washington, D.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInCapital Context triple: [Murder on K Street, setInCapital, Washington, D.C.]
-
A.
possibleCapital
Indicates that a location is a candidate or potential capital city of a given political or administrative entity.
-
B.
capitalizedOn
Indicates that one entity took advantage of, exploited, or made beneficial use of an opportunity, situation, or resource provided or created by another entity.
-
C.
recognizesCapital
Indicates that one entity acknowledges or identifies another entity as the capital of a given region or country.
-
D.
containsCapitalOf
Indicates that one location geographically includes the city that serves as the capital of another region or entity.
-
E.
hasCapital
Indicates that a place or political entity has a specific city designated as its capital.
- F. None of above. chosen
Provenance (4 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61a8bc9e081908b036b5b9773051c |
completed | May 2, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6142a0b988190b404d078f73c3cb9 |
completed | May 2, 2026, 3:11 p.m. |
Created at: April 27, 2026, 4:56 a.m.