Triple
T3030994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ty Cobb |
E82892
|
entity |
| Predicate | timeAsManagerEnd |
P39991
|
FINISHED |
| Object | 1926 |
—
|
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: 1926 | Statement: [Ty Cobb, timeAsManagerEnd, 1926]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeAsManagerEnd Context triple: [Ty Cobb, timeAsManagerEnd, 1926]
-
A.
returnedAsManagerEnd
Indicates that an entity has ceased serving in a managerial role and has returned from a manager position at the specified end point or time.
-
B.
endTimeAtTeam
Indicates the time at which an activity, event, or association concludes for a specific team.
-
C.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
D.
focusPeriodEnd
Indicates the point in time at which a specified focus period or interval concludes.
-
E.
managedUntil
chosen
Indicates that one entity was responsible for managing or overseeing another entity up to a specific point in time.
- 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9aee2fec81908116939a8d773fc4 |
completed | March 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ad961e2a408190afb1759132701305 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.