Triple
T38345097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orange Days |
E1041516
|
entity |
| Predicate | hasTypeOfEpisodeLength |
P11339
|
FINISHED |
| Object | approximately 54 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: approximately 54 minutes | Statement: [Orange Days, hasTypeOfEpisodeLength, approximately 54 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfEpisodeLength Context triple: [Orange Days, hasTypeOfEpisodeLength, approximately 54 minutes]
-
A.
hasEpisodeLengthType
Indicates the type or category of duration associated with an episode (e.g., standard length, short, extended).
-
B.
hasEpisodeRuntime
chosen
Indicates the duration of time that each individual episode of a series or show runs.
-
C.
isEpisodeOfType
Indicates that an episode belongs to or is classified under a specific type or category.
-
D.
hasEpisodeStructure
Indicates that one entity defines or possesses the episodic organization, sequencing, or structural pattern of another (such as a series, season, or narrative work).
-
E.
hasModeEpisode
Indicates that an entity is associated with a particular episode that occurs in or characterizes a specific mode, state, or manner of operation.
- 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_69f76e2ad95481908c920c0e5c1c3e26 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00144238708190acbec3f791cc873e |
completed | May 10, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_6a00120244a4819090ef39070aba9d99 |
completed | May 10, 2026, 5:05 a.m. |
Created at: May 3, 2026, 4:30 p.m.