Triple
T268750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lip Sync Battle |
E5577
|
entity |
| Predicate | runtimePerEpisode |
P1958
|
FINISHED |
| Object | 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: 30 minutes | Statement: [Lip Sync Battle, runtimePerEpisode, 30 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runtimePerEpisode Context triple: [Lip Sync Battle, runtimePerEpisode, 30 minutes]
-
A.
runtimeMinutes
chosen
Indicates the total duration of something, typically a media work or process, measured in minutes.
-
B.
numberOfEpisodes
Indicates the total count of episodes associated with a given entity, such as a series or season.
-
C.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
D.
tempo
Indicates the speed or pace at which an action, process, or sequence unfolds over time.
-
E.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
- 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_69a25853594c8190b05ec3a586ec88bf |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25dae4a0c8190a66cf6ed3889851c |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b70d99c819085d8381a313a2a34 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.