Triple
T17095243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walsh family |
E414829
|
entity |
| Predicate | appearsInTimeframe |
P97182
|
FINISHED |
| Object | late 20th century American television |
—
|
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: late 20th century American television | Statement: [Walsh family, appearsInTimeframe, late 20th century American television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInTimeframe Context triple: [Walsh family, appearsInTimeframe, late 20th century American television]
-
A.
appearsInTimePeriod
chosen
Indicates that an entity is present, active, or occurs within a specified time period.
-
B.
meetsInTimePeriod
Indicates that two entities encounter or come together during a specified time period.
-
C.
appearsInTimePeriodDepicted
Indicates that something is present or occurs within the specific time period that is depicted or represented.
-
D.
occurredBetween
Indicates that an event or action took place within the time interval defined by two temporal boundaries.
-
E.
isSetInTimePeriod
Indicates that an event, story, or situation takes place within a specified time period.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbfc9158819081689d3d594a1908 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.