Triple
T28082005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walt Michaels |
E709704
|
entity |
| Predicate | activeAsPlayerUntil |
P150011
|
FINISHED |
| Object | 1963 |
—
|
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: 1963 | Statement: [Walt Michaels, activeAsPlayerUntil, 1963]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeAsPlayerUntil Context triple: [Walt Michaels, activeAsPlayerUntil, 1963]
-
A.
activeAsPlayerFrom
Indicates that an entity served in the role of a player for another entity starting from a specified point in time.
-
B.
playedProfessionalUntil
chosen
Indicates that an entity participated in a professional-level activity or career up to and including a specified end time or date.
-
C.
retiredAsPlayerFrom
Indicates that an individual ended their professional playing career while being associated with a specific team, organization, or context.
-
D.
laterPlayedFor
Indicates that an individual was a member of or played for a team or organization at a time after a previously referenced team or organization.
-
E.
activeAt
Indicates that an entity is functioning, valid, or in effect during a specified time or at a particular location or context.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 8:52 p.m.