Triple
T23494885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Group B |
E571677
|
entity |
| Predicate | causeOfAbolition |
P800
|
FINISHED |
| Object | safety concerns |
—
|
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: safety concerns | Statement: [Group B, causeOfAbolition, safety concerns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfAbolition Context triple: [Group B, causeOfAbolition, safety concerns]
-
A.
reasonForAbolition
chosen
Indicates the cause, justification, or circumstances that led to something being formally ended or abolished.
-
B.
afterAbolition
Indicates that one event, condition, or state occurs subsequent to the formal ending or abolition of another practice, system, or institution.
-
C.
capitalUntilAbolition
Indicates that an entity served as the capital of another entity up until the point when that capital status was formally abolished.
-
D.
finalAbolition
Indicates the complete and permanent elimination of something, such that it no longer exists or is practiced in any form.
-
E.
slaveryAbolishedBy
Indicates that an instance of slavery was ended, prohibited, or legally abolished by a particular agent, authority, or 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7def8ac8190ade511299078d55b |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:05 p.m.