Triple
T11303953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act of June 28, 1864 |
E267664
|
entity |
| Predicate | broaderProcess |
P98403
|
FINISHED |
| Object | dismantling of slavery’s legal infrastructure in the United States |
—
|
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: dismantling of slavery’s legal infrastructure in the United States | Statement: [Act of June 28, 1864, broaderProcess, dismantling of slavery’s legal infrastructure in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broaderProcess Context triple: [Act of June 28, 1864, broaderProcess, dismantling of slavery’s legal infrastructure in the United States]
-
A.
partOfProcess
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
-
B.
partOfBroaderProgram
Indicates that something is a component, segment, or sub-initiative within a larger overarching program.
-
C.
secondaryProcess
Indicates that an action or process occurs as a secondary, supporting, or subordinate operation relative to a primary process.
-
D.
originProcess
Indicates the process, activity, or mechanism from which an entity, condition, or outcome originally arises or is produced.
-
E.
documentedProcess
Indicates that a process has been formally recorded, described, or specified in documentation.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9a5c3788190ba54eda514b97903 |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787aa31888190860eecaa80da5b20 |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.