Triple
T16404729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamado Jigoku |
E398395
|
entity |
| Predicate | paymentRequired |
P9211
|
FINISHED |
| Object | admission fee |
—
|
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: admission fee | Statement: [Kamado Jigoku, paymentRequired, admission fee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paymentRequired Context triple: [Kamado Jigoku, paymentRequired, admission fee]
-
A.
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.
-
B.
requiresPaymentOf
chosen
Indicates that one entity obligates another entity to provide a specified payment as a condition or requirement.
-
C.
requiresPayerInformation
Indicates that the action or process cannot proceed unless specific information about the payer has been provided.
-
D.
conditionForPayment
Indicates the specific requirement or situation that must be satisfied before a payment is made.
-
E.
creditCheckRequired
Indicates that a verification of an entity’s creditworthiness must be performed before proceeding with a related action or transaction.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327d1f16481909adb19dab86dcc72 |
completed | April 18, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.