Triple
T38443567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Every Grain of Sand |
E906572
|
entity |
| Predicate | hasLyricAllusionTo |
P114550
|
FINISHED |
| Object | Bible |
—
|
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: Bible | Statement: [Every Grain of Sand, hasLyricAllusionTo, Bible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLyricAllusionTo Context triple: [Every Grain of Sand, hasLyricAllusionTo, Bible]
-
A.
hasLyricsMentioning
chosen
Indicates that the referenced lyrics explicitly mention or refer to the specified entity.
-
B.
hasLyricsIn
Indicates that the lyrics of a work are written or available in a specified language.
-
C.
usesLyricalElementsFrom
Indicates that one work incorporates or borrows lyrical components (such as words, phrases, or stylistic features) from another work.
-
D.
hasRefrainRelatedTo
Indicates that a refrain (repeated musical or textual section) in one work is thematically or content-wise related to another specified subject or element.
-
E.
hasEnigmaticLyrics
Indicates that the lyrics associated with an entity are mysterious, obscure, or difficult to interpret.
- 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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcce7afcd08190906cc3801152656a |
completed | May 7, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69fcccf140ec8190862d53388a5f40d7 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.