Triple
T38629110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talmadge sisters |
E937399
|
entity |
| Predicate | notableActivityEnd |
P17625
|
FINISHED |
| Object | 1920s |
—
|
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: 1920s | Statement: [Talmadge sisters, notableActivityEnd, 1920s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableActivityEnd Context triple: [Talmadge sisters, notableActivityEnd, 1920s]
-
A.
endOfActivity
chosen
Indicates that a particular activity has reached its completion or final point in time.
-
B.
notableActivityIn
Indicates that an entity is particularly recognized for performing a significant activity within a specified place, context, or domain.
-
C.
significantEventEnd
Indicates the point in time when a significant event or occurrence comes to a close or is considered finished.
-
D.
activityEndedBecauseOf
Indicates that an activity has come to an end specifically due to a particular cause, condition, or event.
-
E.
activityEndContext
Indicates the situational or environmental context in which an activity concludes or comes to an end.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.