Triple
T37307284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jehovah’s Witnesses publications |
E926112
|
entity |
| Predicate | oftenProvided |
P65734
|
FINISHED |
| Object | without charge |
—
|
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: without charge | Statement: [Jehovah’s Witnesses publications, oftenProvided, without charge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenProvided Context triple: [Jehovah’s Witnesses publications, oftenProvided, without charge]
-
A.
oftenProvides
chosen
Indicates that one entity frequently or regularly supplies, offers, or makes another entity available.
-
B.
sometimesProvides
Indicates that one entity occasionally or intermittently provides something (such as a service, resource, or support) to another entity, but not on a consistent or guaranteed basis.
-
C.
oftenFrom
Indicates that something frequently originates, derives, or comes from a particular source or location.
-
D.
oftenHave
Indicates that one entity frequently possesses, experiences, or is associated with another entity.
-
E.
oftenGivenTo
Indicates that something is frequently provided, granted, or presented to a particular 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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: May 3, 2026, 4:16 p.m.