Triple
T28082004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walt Michaels |
E709704
|
entity |
| Predicate | activeAsPlayerFrom |
P171780
|
FINISHED |
| Object | 1951 |
—
|
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: 1951 | Statement: [Walt Michaels, activeAsPlayerFrom, 1951]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeAsPlayerFrom Context triple: [Walt Michaels, activeAsPlayerFrom, 1951]
-
A.
playsAs
Indicates that one entity performs, portrays, or assumes the role, character, or persona of another entity.
-
B.
activeAsPlaywrightFrom
Indicates the time period during which an entity was actively working in the role of a playwright.
-
C.
formerPlayerType
Indicates that an entity previously had a specific player role or classification but no longer holds that status.
-
D.
isKeyPlayerFor
Indicates that an entity plays a crucial or central role in the success, functioning, or performance of another entity (such as a team, project, or organization).
-
E.
hasPlayer
Indicates that an entity (such as a team, game, or roster) includes or is associated with a specific player.
- F. None of above. chosen
Provenance (4 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_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a28b8ea881908733485374771c51 |
completed | May 3, 2026, 1:19 a.m. |
Created at: April 27, 2026, 8:52 p.m.