Triple
T10361290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurram Agency |
E244138
|
entity |
| Predicate | abolishedAsAgency |
P31451
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Kurram Agency, abolishedAsAgency, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abolishedAsAgency Context triple: [Kurram Agency, abolishedAsAgency, 2018]
-
A.
abolishesAgencyBy
Indicates that one entity formally ends, revokes, or eliminates the authority, function, or existence of another entity or agency.
-
B.
abolishedAsSystem
chosen
Indicates that something (typically an institution, practice, or system) has been officially ended and no longer exists as an organized or recognized system.
-
C.
abolishedDuring
Indicates that an entity or practice ceased to exist or was officially ended within the time period defined by another entity.
-
D.
abolishedAfter
Indicates that one entity was abolished at a later time than another entity was abolished.
-
E.
dissolvedOrAbolishedBy
Indicates that an entity (such as an organization, institution, or legal body) ceased to exist as a result of a specific dissolving or abolishing action carried out by another entity or authority.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e96209548190957368ee8c6a9ec3 |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dfa657f481909cc5cc8fec00ad19 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:59 a.m.