Triple
T12976700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Desperate Housewives (theme) |
E321542
|
entity |
| Predicate | hasDurationCategory |
P47557
|
FINISHED |
| Object | short theme |
—
|
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: short theme | Statement: [Desperate Housewives (theme), hasDurationCategory, short theme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDurationCategory Context triple: [Desperate Housewives (theme), hasDurationCategory, short theme]
-
A.
hasDurationType
Indicates that something is associated with a specific kind or category of duration (e.g., temporary, permanent, short-term, long-term).
-
B.
hasOfficialDuration
Indicates the formally defined length of time associated with an event, process, or entity.
-
C.
durationCategory
chosen
Indicates the classification of an event or state based on how long it lasts, grouping it into a specific duration range or type.
-
D.
hasRunningTimeCategory
Indicates that an entity is associated with a specific category based on its running time or duration.
-
E.
possibleDuration
Indicates the range or specific length of time that an action, event, or state can last or is allowed to last.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:38 p.m.