Triple
T26044632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle Leoch |
E647792
|
entity |
| Predicate | timeframeOfMainEvents |
P145541
|
FINISHED |
| Object | 1740s (in fiction) |
—
|
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: 1740s (in fiction) | Statement: [Castle Leoch, timeframeOfMainEvents, 1740s (in fiction)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeframeOfMainEvents Context triple: [Castle Leoch, timeframeOfMainEvents, 1740s (in fiction)]
-
A.
timeBetweenMainEvents
Indicates the duration or interval separating two primary or key events in a sequence or process.
-
B.
timePeriodOfMajorImportance
Indicates that a particular time period holds significant importance or prominence within a given context or domain.
-
C.
timeCoMainEvent
Indicates that two or more events occur as co-main events at the same time or within the same overarching event timeframe.
-
D.
notableEventPeriod
chosen
Indicates the time span during which a notable or significant event associated with an entity took place.
-
E.
timePeriodEvent
Indicates that an event occurs, is scheduled, or is valid 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f606597b48819084ffefda1f2dfc8f |
completed | May 2, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:09 a.m.