Triple
T27220892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eston Hemings |
E681264
|
entity |
| Predicate | emancipatedBy |
P23989
|
FINISHED |
| Object | Thomas Jefferson’s will |
—
|
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: Thomas Jefferson’s will | Statement: [Eston Hemings, emancipatedBy, Thomas Jefferson’s will]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emancipatedBy Context triple: [Eston Hemings, emancipatedBy, Thomas Jefferson’s will]
-
A.
emancipatedIn
Indicates that an entity was legally freed or released from bondage, control, or restrictions in a specific place or jurisdiction.
-
B.
emancipated
chosen
Indicates that one entity has been freed from the control, authority, or legal dependency of another.
-
C.
estimatedNumberEmancipated
Indicates the estimated count of individuals who have been emancipated.
-
D.
ageWhenFreed
Indicates the age an individual was at the time they were freed from a prior state of bondage, captivity, or restriction.
-
E.
beneficiariesOfEmancipation
Indicates that the subject is a person or group who gains rights, freedoms, or advantages as a result of an emancipation event or process.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6261ff6c481908b40edb19d5a7f3b |
completed | May 2, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:42 a.m.