Triple
T32406920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Betrothed |
E828108
|
entity |
| Predicate | setInYears |
P92184
|
FINISHED |
| Object | 1628–1630 |
—
|
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: 1628–1630 | Statement: [The Betrothed, setInYears, 1628–1630]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInYears Context triple: [The Betrothed, setInYears, 1628–1630]
-
A.
setYearsBefore
Indicates that one event, state, or time point occurs a specified number of years before another reference event or time.
-
B.
appliesInYears
chosen
Indicates that something (such as a rule, condition, or effect) is valid, relevant, or in force during specific years.
-
C.
alsoSetInYear
Indicates that two works or events share the same setting year.
-
D.
durationInYears
Indicates the length of time associated with something, measured in whole or fractional years.
-
E.
countsYearsFrom
Indicates a temporal relationship where the number of years is measured starting from a specified reference point or event.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c247928481908f5aa369adfd2906 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:53 a.m.