Triple
T3330840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slave Trade Act 1843 |
E70028
|
entity |
| Predicate | appliesToConcept |
P531
|
FINISHED |
| Object | transatlantic slave trade |
—
|
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: transatlantic slave trade | Statement: [Slave Trade Act 1843, appliesToConcept, transatlantic slave trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToConcept Context triple: [Slave Trade Act 1843, appliesToConcept, transatlantic slave trade]
-
A.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
B.
hasConcept
chosen
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
C.
appliesPrimarilyTo
Indicates that a property, rule, or characteristic is mainly relevant or intended for a particular entity or group, more than for others.
-
D.
appliesToFeature
Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
-
E.
appliesToPerson
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific person.
- 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb191e1988190a1d88596f6605aff |
completed | March 8, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69ada42c2ba8819091136805ce17b39d |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.