Triple
T38443574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Every Grain of Sand |
E906572
|
entity |
| Predicate | hasDemoVersion |
P49902
|
FINISHED |
| Object | Biograph |
—
|
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: Biograph | Statement: [Every Grain of Sand, hasDemoVersion, Biograph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDemoVersion Context triple: [Every Grain of Sand, hasDemoVersion, Biograph]
-
A.
hasAcousticDemoVersion
Indicates that an entity has a version or recording presented in an acoustic demo form.
-
B.
hasDemonstration
chosen
Indicates that one entity includes, is accompanied by, or is associated with a demonstration or illustrative example of another entity or concept.
-
C.
isDemoOf
Indicates that one entity serves as a demonstration, example, or illustrative instance of another entity.
-
D.
hasDemonstrationsSince
Indicates that one entity has held or experienced demonstrations continuously or repeatedly starting from a specified point in time.
-
E.
hasDownloadableVersion
Indicates that an entity has a version or instance that can be obtained by downloading it in some digital form.
- 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_69ffdd05d1908190957deb11392f4595 |
completed | May 10, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69ffdc0d33c881908b3483bee8a96540 |
completed | May 10, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:31 p.m.