Triple
T28878690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zana |
E732351
|
entity |
| Predicate | basedOnWorkReleasePeriod |
P191791
|
FINISHED |
| Object | 1993 television season |
—
|
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: 1993 television season | Statement: [Zana, basedOnWorkReleasePeriod, 1993 television season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnWorkReleasePeriod Context triple: [Zana, basedOnWorkReleasePeriod, 1993 television season]
-
A.
basedOnWorkPeriod
Indicates that something is determined, calculated, or defined according to a specific period of work or employment.
-
B.
workReleasePeriod
Indicates the time span during which a person is authorized to leave confinement or regular duties to perform work under a work-release arrangement.
-
C.
basedOnWorkDirector
Indicates that one entity serves as the director of a work on which another entity is based.
-
D.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
E.
isFromWorkReleasedBy
Indicates that something originates from or is derived from a work that was released by a particular agent or entity.
- F. None of above. chosen
Provenance (4 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
| PDg | Predicate description generation | batch_69fcec5e560481909cd710b88897e833 |
completed | May 7, 2026, 7:47 p.m. |
Created at: April 28, 2026, 7:40 a.m.