Triple
T7647599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadwell plantation |
E173163
|
entity |
| Predicate | employedSystem |
P77807
|
FINISHED |
| Object | 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: slavery | Statement: [Shadwell plantation, employedSystem, slavery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employedSystem Context triple: [Shadwell plantation, employedSystem, slavery]
-
A.
employedPeople
Indicates that there exists a relationship where people are currently working in jobs or positions, typically under an employer.
-
B.
employedRole
Indicates that an entity holds or performs a specific role or position within an employment or work context.
-
C.
employedApproximately
Indicates that one entity employs another in a manner where the number, duration, or extent of employment is approximate rather than exact.
-
D.
employmentType
Indicates the specific kind or category of employment relationship that exists between an individual and an employer (e.g., full-time, part-time, contract).
-
E.
employerIn
Indicates that one entity serves as the employer of another within a specified context, such as a location, organization, or time period.
- 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_69c6995360188190968ee57b72a1627f |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faf6328c8190bce0a3f8a17ef890 |
completed | March 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e9ef1c81909c8bff716541ac1f |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8195e5c8190835e28d44e19f6ef |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:58 p.m.