Triple
T14697552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Garner |
E345202
|
entity |
| Predicate | upholdsSystem |
P101852
|
FINISHED |
| Object | chattel slavery |
—
|
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: chattel slavery | Statement: [Mr. Garner, upholdsSystem, chattel slavery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upholdsSystem Context triple: [Mr. Garner, upholdsSystem, chattel slavery]
-
A.
upheldBy
Indicates that one entity is supported, maintained, or validated by another, often through approval, enforcement, or confirmation of its validity.
-
B.
holdsUnder
Indicates that one entity maintains possession, control, or validity of another entity subject to certain conditions, constraints, or a specific context.
-
C.
holdsTo
chosen
Indicates that one entity maintains, adheres, or remains committed to another entity, such as a belief, standard, agreement, or condition.
-
D.
followsPolityOf
Indicates that one entity adopts, adheres to, or operates under the political system, governance model, or policy framework established by another entity.
-
E.
holdsIn
Indicates that a relationship, condition, or event is valid or occurs within a specified time interval or temporal context.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb604f88081908a677175045496d0 |
completed | April 14, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.