Triple
T10905826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Good Place |
E257565
|
entity |
| Predicate | originalRuntimePerEpisode |
P11339
|
FINISHED |
| Object | 22 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: 22 minutes | Statement: [The Good Place, originalRuntimePerEpisode, 22 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalRuntimePerEpisode Context triple: [The Good Place, originalRuntimePerEpisode, 22 minutes]
-
A.
hasEpisodeRuntime
chosen
Indicates the duration of time that each individual episode of a series or show runs.
-
B.
typicalRuntimePerShort
Indicates the usual or average amount of time it takes to complete a short instance of the referenced activity or process.
-
C.
runningTimeMiniSeriesVersion
Indicates the duration of the mini-series version of a work, typically measured in time units such as minutes.
-
D.
originalRuntime
Indicates the initial or primary duration associated with something, typically before any edits, changes, or adjustments are made.
-
E.
primaryRuntime
Indicates the main runtime environment or platform under which an entity (such as a program, service, or component) is intended to execute.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7706679b48190a1f29fc64fe8a334 |
completed | April 9, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.