Triple
T18834909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rumpelstiltskin |
E460635
|
entity |
| Predicate | demandsAsPayment |
P9211
|
FINISHED |
| Object | firstborn child |
—
|
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: firstborn child | Statement: [Rumpelstiltskin, demandsAsPayment, firstborn child]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demandsAsPayment Context triple: [Rumpelstiltskin, demandsAsPayment, firstborn child]
-
A.
requiresPaymentOf
chosen
Indicates that one entity obligates another entity to provide a specified payment as a condition or requirement.
-
B.
requiresPaymentIn
Indicates that one entity must be paid in a specified currency or payment medium in order for a related action, service, or obligation to be fulfilled.
-
C.
conditionForPayment
Indicates the specific requirement or situation that must be satisfied before a payment is made.
-
D.
demands
Indicates that one entity insists that another entity provide something or take a specific action, typically with authority or urgency.
-
E.
promptedDemandFor
Indicates that one entity’s action or occurrence caused an increase in demand for another entity.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99c1394819095c62eef040e552c |
completed | April 20, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.