Triple
T4776313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jock |
E106055
|
entity |
| Predicate | hasMeaningViaJohn |
P59250
|
FINISHED |
| Object | Yahweh is gracious |
—
|
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: Yahweh is gracious | Statement: [Jock, hasMeaningViaJohn, Yahweh is gracious]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeaningViaJohn Context triple: [Jock, hasMeaningViaJohn, Yahweh is gracious]
-
A.
possibleMeaning
Indicates that something may plausibly represent, signify, or be interpreted as a particular meaning or sense.
-
B.
letterMeaning
Indicates that a particular letter conveys a specific meaning, interpretation, or semantic content.
-
C.
stringMeaning
Indicates that one entity represents the semantic content or interpretation of a given string associated with another entity.
-
D.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
-
E.
hasLiteralMeaning
Indicates that one entity expresses the direct, explicit meaning or sense of another entity (such as a word, phrase, or symbol).
- 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_69bd43f3074c8190937e7b0a457fe9f1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd69237f80819090713ed62653fb75 |
completed | March 20, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69bd622be1388190ab5511b589c878c0 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd6922407481908565ed0b1dac2b30 |
completed | March 20, 2026, 3:34 p.m. |
Created at: March 20, 2026, 1:21 p.m.