Triple
T14312543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania attorneys |
E354867
|
entity |
| Predicate | mustPay |
P9211
|
FINISHED |
| Object | annual attorney registration 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: annual attorney registration fee | Statement: [Pennsylvania attorneys, mustPay, annual attorney registration fee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mustPay Context triple: [Pennsylvania attorneys, mustPay, annual attorney registration fee]
-
A.
requiresPaymentOf
chosen
Indicates that one entity obligates another entity to provide a specified payment as a condition or requirement.
-
B.
repaymentRequirement
Indicates that one party is obligated to pay back money or value to another party under specified terms or conditions.
-
C.
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.
-
D.
paidBy
Indicates that a payment or financial obligation is made or settled by the specified entity.
-
E.
paidFor
Indicates that one entity provided payment to cover the cost of something on behalf of 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b386d0819087d14f3ce84a1997 |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:12 a.m.