Triple
T11965815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Creation |
E284787
|
entity |
| Predicate | hasOriginalLibrettoVersion |
P78807
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [The Creation, hasOriginalLibrettoVersion, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalLibrettoVersion Context triple: [The Creation, hasOriginalLibrettoVersion, English]
-
A.
originalLanguageOfLibretto
chosen
Indicates the language in which a libretto was originally written for a given work.
-
B.
includesLibretto
Indicates that one entity (typically a musical or operatic work or publication) contains or is accompanied by the full text/libretto of another work.
-
C.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
-
D.
hasUnabridgedOriginalPoet
Indicates that something (such as a work or edition) is associated with the poet of the complete, unabridged original version.
-
E.
hasKaraokeVersion
Indicates that an entity has a corresponding karaoke (instrumental or sing-along) version of itself.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903799f948190a5dc4d3822f3ff27 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:46 p.m.