Triple
T36418850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry Wolverton |
E897091
|
entity |
| Predicate | teamManagedSeason |
P96379
|
FINISHED |
| Object | New York Highlanders 1912 season |
—
|
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: New York Highlanders 1912 season | Statement: [Harry Wolverton, teamManagedSeason, New York Highlanders 1912 season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamManagedSeason Context triple: [Harry Wolverton, teamManagedSeason, New York Highlanders 1912 season]
-
A.
teamManagedDuringSeason
chosen
Indicates that one entity served as the manager or head coach of a team for the duration of a specified season.
-
B.
teamManagedLeague
Indicates that a team is responsible for managing or overseeing the operations of a particular league.
-
C.
teamManagedBy
Indicates that a particular team is under the management or supervision of a specified manager or managing entity.
-
D.
currentTeamManaged
Indicates that an entity is the team currently being managed by another entity.
-
E.
leagueManaged
Indicates that a league has administrative or organizational control over another entity, such as a team, event, or competition.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.