Triple
T35758725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avodah |
E1033515
|
entity |
| Predicate | alsoConnotes |
P4340
|
FINISHED |
| Object | service to God |
—
|
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: service to God | Statement: [Avodah, alsoConnotes, service to God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoConnotes Context triple: [Avodah, alsoConnotes, service to God]
-
A.
hasConnotation
chosen
Indicates that one entity carries an implied or associated meaning, tone, or emotional nuance in relation to another entity.
-
B.
hasPositiveConnotation
Indicates that something is associated with favorable, pleasant, or approving meanings, feelings, or implications.
-
C.
etymologicalConnotation
Indicates that one term carries a particular historical or origin-based nuance, implication, or association derived from its etymology in relation to another term or concept.
-
D.
alsoConsidered
Indicates that one item is regarded as an alternative or additional option alongside another in a given context.
-
E.
socialConnotation
Indicates the commonly understood social meaning, implication, or value judgment that people associate with something within a given cultural or social context.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a1c2030881908aeb62c4eba771d7 |
completed | May 3, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.