Triple
T26873279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murder Inside the Beltway |
E676672
|
entity |
| Predicate | BeltwayRefersTo |
P161552
|
FINISHED |
| Object | political establishment in Washington, D.C. |
—
|
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: political establishment in Washington, D.C. | Statement: [Murder Inside the Beltway, BeltwayRefersTo, political establishment in Washington, D.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BeltwayRefersTo Context triple: [Murder Inside the Beltway, BeltwayRefersTo, political establishment in Washington, D.C.]
-
A.
beltwayDesignation
Indicates that a roadway has been designated as part of a beltway or ring road encircling an area.
-
B.
beltwayName
Indicates that a beltway (ring road or orbital highway) has a specific name.
-
C.
beltwayAround
Indicates that one roadway or route functions as a beltway encircling or surrounding another specified area or location.
-
D.
beltwayType
Indicates the specific classification or type of a beltway (ring road) associated with a given roadway or area.
-
E.
outerBeltwayFor
Indicates that one roadway or route functions as an outer beltway encircling or bypassing the area served by another route or location.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61f160fec819088561cb2020a2b69 |
completed | May 2, 2026, 3:58 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, 5:34 a.m.