Triple
T19299793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D’Ortega |
E482662
|
entity |
| Predicate | offersAsPayment |
P63281
|
FINISHED |
| Object | enslaved people |
—
|
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: enslaved people | Statement: [D’Ortega, offersAsPayment, enslaved people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersAsPayment Context triple: [D’Ortega, offersAsPayment, enslaved people]
-
A.
hasPaymentOption
Indicates that an entity supports or offers a particular method or option for making payments.
-
B.
paymentServices
Indicates that one entity provides or facilitates payment-related services or processing for another entity.
-
C.
offersObject
chosen
Indicates that a subject provides or makes available a specific object to another party as an offer.
-
D.
offersServiceIn
Indicates that a provider makes a particular service available within a specified location or jurisdiction.
-
E.
canPay
Indicates that one entity has the ability or authorization to make a payment to another entity or to settle a specified obligation.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc895c68819096d06746f1b84e06 |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:31 p.m.