Triple
T12306149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBC lightweight title |
E293356
|
entity |
| Predicate | requiresSanctioningFee |
P87382
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [WBC lightweight title, requiresSanctioningFee, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSanctioningFee Context triple: [WBC lightweight title, requiresSanctioningFee, true]
-
A.
feeRequirement
chosen
Indicates that a payment or fee must be provided or satisfied as a condition for a particular action, service, or relationship to occur or remain valid.
-
B.
requiresPaymentOf
Indicates that one entity obligates another entity to provide a specified payment as a condition or requirement.
-
C.
requiresSanctioningBody
Indicates that an action, event, or decision must be approved or authorized by a designated sanctioning authority or governing body.
-
D.
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.
-
E.
fareRequired
Indicates that a payment or fare is required for access to or use of a service, route, or transportation option.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.