Triple
T15039430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | What the Dog Saw |
E378559
|
entity |
| Predicate | containsWorkFromPeriod |
P116502
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [What the Dog Saw, containsWorkFromPeriod, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsWorkFromPeriod Context triple: [What the Dog Saw, containsWorkFromPeriod, 1990s]
-
A.
hasWorkPeriod
Indicates that an entity is associated with a specific span of time during which it performs or is engaged in some work or activity.
-
B.
partOfWorkPeriod
Indicates that a specific time span is contained within, and belongs to, a larger defined work period.
-
C.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
D.
hasWorkPart
Indicates that one work is a component, section, or constituent part of another, larger work.
-
E.
hasWorkSchedule
Indicates that an entity is assigned or follows a specific work schedule, defining when they are expected to work.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded82e79a481908ddb9609af8c4407 |
completed | April 15, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 3 a.m.