Triple
T4446134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wetmore family |
E96292
|
entity |
| Predicate | timeframeEnd |
P35136
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Wetmore family, timeframeEnd, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeframeEnd Context triple: [Wetmore family, timeframeEnd, early 20th century]
-
A.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
B.
focusPeriodEnd
chosen
Indicates the point in time at which a specified focus period or interval concludes.
-
C.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
D.
timeFrameSpecified
Indicates that a specific temporal period or duration has been explicitly defined or constrained for the related event, action, or relationship.
-
E.
endDateOfEntries
Indicates the date on which the referenced entries conclude or are no longer valid.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355d1eba08190899d0a3c1684ce4e |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.