Triple
T27640031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E-meter |
E696563
|
entity |
| Predicate | hasLegalDisclaimer |
P70991
|
FINISHED |
| Object | for religious use only |
—
|
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: for religious use only | Statement: [E-meter, hasLegalDisclaimer, for religious use only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalDisclaimer Context triple: [E-meter, hasLegalDisclaimer, for religious use only]
-
A.
hasLiabilityDisclaimer
chosen
Indicates that an entity includes or is associated with a statement limiting or excluding legal responsibility for certain actions, outcomes, or information.
-
B.
hasWarrantyDisclaimer
Indicates that a product, service, or agreement includes a statement limiting or denying warranties or liability.
-
C.
hasComplianceStatement
Indicates that an entity is associated with a formal declaration that it adheres to specified rules, standards, or regulatory requirements.
-
D.
hasLegalResponse
Indicates that an entity has an associated legal reply, action, or measure taken in response to a legal situation, claim, or requirement.
-
E.
legalIn
Indicates that an action, status, or entity is permitted or valid under the laws or regulations of a specified jurisdiction.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 27, 2026, 2:26 p.m.