Triple
T357462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York's 28th congressional district |
E7575
|
entity |
| Predicate | eliminatedIn |
P1466
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [New York's 28th congressional district, eliminatedIn, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eliminatedIn Context triple: [New York's 28th congressional district, eliminatedIn, 2013]
-
A.
loserElimination
Indicates that the entity identified as the loser in a competition, game, or contest is removed or disqualified from further participation.
-
B.
repealed
Indicates that a law, rule, or regulation has been officially revoked or annulled so that it no longer has legal effect.
-
C.
withdrewFrom
Indicates that one entity removed itself or its participation from another entity, context, or arrangement it was previously part of.
-
D.
concludedBy
Indicates that an event, process, or state is brought to an end or finalized by a specific agent or entity.
-
E.
discontinuedIn
chosen
Indicates that an item, product, or service stopped being produced, offered, or supported starting in a specified time or place.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebaf0c9881909313f98818e7fa58 |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e959ce948190a201c017eecb7c95 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.