Triple
T22875305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Star |
E567304
|
entity |
| Predicate | lengthLiveVersion |
P33220
|
FINISHED |
| Object | often between 15 and 30 minutes |
—
|
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: often between 15 and 30 minutes | Statement: [Dark Star, lengthLiveVersion, often between 15 and 30 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lengthLiveVersion Context triple: [Dark Star, lengthLiveVersion, often between 15 and 30 minutes]
-
A.
longVersionLength
chosen
Indicates that one entity specifies the length or duration of a more detailed or extended version of another entity.
-
B.
isLiveVersion
Indicates that one entity is the current, active, or publicly available version of another entity.
-
C.
liveVersionReleasedOn
Indicates the date or time when a live version of something (such as a product, feature, or content) is officially released or made available.
-
D.
hasLiveVersions
Indicates that an entity has one or more recorded or documented live-performance versions of itself.
-
E.
liveVersionRecordedAt
Indicates that a live version of something (such as a performance or recording) was recorded at a specific place or event.
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f57a1ec8190b8c6a0080d97a2a2 |
completed | April 29, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69eed2d8c0608190afef4c4e530c0e2c |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:39 p.m.