Triple
T19929027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naboth |
E479001
|
entity |
| Predicate | chargesWere |
P137876
|
FINISHED |
| Object | fabricated |
—
|
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: fabricated | Statement: [Naboth, chargesWere, fabricated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargesWere Context triple: [Naboth, chargesWere, fabricated]
-
A.
chargedOn
Indicates that a fee, cost, or financial amount is applied to an account, entity, or transaction at a specific time or in connection with a particular event.
-
B.
chargesBasedOn
Indicates that one party determines or applies a fee, price, or cost to another party or item according to a specified basis, criterion, or reference.
-
C.
chargesVia
Indicates that one entity charges or powers another entity using a specified medium, method, or interface.
-
D.
chargesFeeFor
Indicates that one entity requires payment of a fee from another entity in exchange for a specific service, product, or privilege.
-
E.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659cd4500819090363a4b7d6bf193 |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:53 p.m.