Triple
T3179276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abolition of slavery in the British Empire |
E66539
|
entity |
| Predicate | effectiveDateInJamaica |
P1260
|
FINISHED |
| Object | 1834 |
—
|
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: 1834 | Statement: [Abolition of slavery in the British Empire, effectiveDateInJamaica, 1834]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveDateInJamaica Context triple: [Abolition of slavery in the British Empire, effectiveDateInJamaica, 1834]
-
A.
dateOfEnactment
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
-
B.
dateEnacted
chosen
Indicates the date on which a law, policy, or formal measure was officially put into effect or became legally operative.
-
C.
extensionEffectiveDate
Indicates the date on which an extension to an existing agreement, term, or condition becomes effective.
-
D.
dateGranted
Indicates the specific date on which a right, status, or permission was formally conferred or approved.
-
E.
legalDefinitionCameIntoForce
Indicates that a particular legal definition officially became valid and enforceable from a specified point in time.
- 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada69f2d108190847922795e7b6687 |
completed | March 8, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69ad9e02677c8190a21d93b1259b2761 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.