Triple
T16952939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A State of Trance |
E411227
|
entity |
| Predicate | typicalEpisodeDuration |
P11339
|
FINISHED |
| Object | approximately 2 hours |
—
|
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: approximately 2 hours | Statement: [A State of Trance, typicalEpisodeDuration, approximately 2 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEpisodeDuration Context triple: [A State of Trance, typicalEpisodeDuration, approximately 2 hours]
-
A.
typicalViewingTime
Indicates the usual or most common amount of time an entity is viewed or watched under normal circumstances.
-
B.
hasEpisodeLengthType
Indicates the type or category of duration associated with an episode (e.g., standard length, short, extended).
-
C.
hasEpisodeRuntime
chosen
Indicates the duration of time that each individual episode of a series or show runs.
-
D.
televisionSeriesRuntimeCharacteristic
Indicates a relationship where a television series is associated with a specific runtime-related characteristic, such as typical episode length or overall duration pattern.
-
E.
typicalRecordingDuration
Indicates the usual or standard length of time that something is recorded.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d01a4ae8819085a6ce01fbc71b0f |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.