Triple
T2362374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fugitive Slave Clause |
E47302
|
entity |
| Predicate | doesNotUseTerm |
P2558
|
FINISHED |
| Object | slave |
—
|
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: slave | Statement: [Fugitive Slave Clause, doesNotUseTerm, slave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotUseTerm Context triple: [Fugitive Slave Clause, doesNotUseTerm, slave]
-
A.
doesNotUse
chosen
Indicates that one entity intentionally refrains from employing, utilizing, or relying on another entity, method, or resource.
-
B.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
C.
notPreferredTermFor
Indicates that one term is a non-preferred or deprecated label that should be replaced by another, preferred term in a controlled vocabulary or terminology system.
-
D.
doesNotStandFor
Indicates that one entity does not represent, symbolize, or act on behalf of another entity in any capacity.
-
E.
doesNotConsider
Indicates that one entity fails or chooses not to take another entity or factor into account when forming judgments, decisions, or actions.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc74501388190adce9b3e51a03ded |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc599b92c819093d9e15d4437705d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:55 p.m.