Triple
T17612125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Dog Skip |
E428987
|
entity |
| Predicate | timeSettingIncludes |
P110613
|
FINISHED |
| Object | World War II era |
—
|
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: World War II era | Statement: [My Dog Skip, timeSettingIncludes, World War II era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSettingIncludes Context triple: [My Dog Skip, timeSettingIncludes, World War II era]
-
A.
timeSpanIncludes
chosen
Indicates that one time span fully contains or covers the entire duration of another time span.
-
B.
timeOfSetting
Indicates the specific time at which an event, object, or phenomenon is set, scheduled, or takes place.
-
C.
timeType
Indicates the specific temporal category or classification associated with a time-related entity or value (e.g., duration, point in time, interval, or recurrence type).
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
timeProperty
Indicates that one entity specifies, constrains, or characterizes a temporal aspect or timing-related attribute of another entity.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d2dfa688190a0b9b396bb6133cc |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.