Triple
T4757093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charon |
E105614
|
entity |
| Predicate | paymentPlaced |
P58586
|
FINISHED |
| Object | in mouth of the dead |
—
|
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: in mouth of the dead | Statement: [Charon, paymentPlaced, in mouth of the dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paymentPlaced Context triple: [Charon, paymentPlaced, in mouth of the dead]
-
A.
paidFor
Indicates that one entity provided payment to cover the cost of something on behalf of another entity.
-
B.
paidBy
Indicates that a payment or financial obligation is made or settled by the specified entity.
-
C.
hasPayStatus
Indicates the current payment state or condition associated with an entity, such as whether an amount is paid, unpaid, pending, or otherwise resolved.
-
D.
repaymentOutcome
Indicates the result or status of a repayment action, such as whether it was completed, failed, or partially fulfilled.
-
E.
paymentAmount
Indicates the specific monetary value involved in a payment transaction between parties.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64ec16a0819089836e4388b555f6 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd6424a1d08190ac1d5fc574dc1b55 |
completed | March 20, 2026, 3:13 p.m. |
Created at: March 20, 2026, 1:20 p.m.