Triple
T32902686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daland |
E841652
|
entity |
| Predicate | offersDaughterTo |
P22295
|
FINISHED |
| Object | the Dutchman |
—
|
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: the Dutchman | Statement: [Daland, offersDaughterTo, the Dutchman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersDaughterTo Context triple: [Daland, offersDaughterTo, the Dutchman]
-
A.
offersConnectionTo
Indicates that one entity provides or enables access, linkage, or connectivity to another entity.
-
B.
offersChoiceTo
Indicates that one entity presents one or more options for selection to another entity.
-
C.
offeredRewardTo
Indicates that one entity has proposed or promised a reward to another entity, typically as an incentive for a specific action or outcome.
-
D.
offering
chosen
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
-
E.
rewardOfferedBy
Indicates that a reward is provided or promised by one entity to another, typically as an incentive or compensation for a specific action or outcome.
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: May 1, 2026, 1:19 a.m.