Triple
T31857841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Canon |
E813243
|
entity |
| Predicate | refrainAddressedTo |
P130146
|
FINISHED |
| Object | God |
—
|
NE NERFINISHED |
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: God | Statement: [Great Canon, refrainAddressedTo, God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refrainAddressedTo Context triple: [Great Canon, refrainAddressedTo, God]
-
A.
refrain
Indicates that an entity deliberately holds back from performing a particular action or behavior.
-
B.
refrainTranslation
Indicates that one expression is a translation of the repeated or recurring part (refrain) of another expression, typically in a different language.
-
C.
storyAddressedTo
Indicates that a story is specifically directed or intended for a particular recipient or audience.
-
D.
refrainText
Indicates that a piece of text functions as the recurring refrain or repeated line within a larger work, such as a song or poem.
-
E.
hasRefrainRelatedTo
chosen
Indicates that a refrain (repeated musical or textual section) in one work is thematically or content-wise related to another specified subject or element.
- 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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b06b872481908372becd54a1792e |
completed | May 3, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:52 p.m.