Triple
T26044607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle Leoch |
E647792
|
entity |
| Predicate | usedAsRecurringSettingInSeason |
P153979
|
FINISHED |
| Object | Outlander season 2 |
—
|
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: Outlander season 2 | Statement: [Castle Leoch, usedAsRecurringSettingInSeason, Outlander season 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsRecurringSettingInSeason Context triple: [Castle Leoch, usedAsRecurringSettingInSeason, Outlander season 2]
-
A.
recurringSeriesSettingFor
chosen
Indicates that something serves as the setting or context in which a recurring series regularly takes place.
-
B.
recurringDuring
Indicates that an event or state happens repeatedly within the time span or context defined by another event or interval.
-
C.
usedInSeason
Indicates that something (such as an item, strategy, or element) is utilized or appears within a particular season.
-
D.
recurringSegmentOn
Indicates that one entity appears repeatedly as a regular segment or feature within another entity, such as a show, publication, or series.
-
E.
hasUseSeason
Indicates the season or time of year during which something is intended or suitable to be used.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 22, 2026, 9:09 a.m.