Triple
T25962820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John T. Powers |
E645585
|
entity |
| Predicate | leagueOrganized |
P66784
|
FINISHED |
| Object | Federal League |
—
|
NE NERFINISHED |
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: Federal League | Statement: [John T. Powers, leagueOrganized, Federal League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueOrganized Context triple: [John T. Powers, leagueOrganized, Federal League]
-
A.
leagueOrganization
Indicates that an organization is responsible for running, governing, or officially managing a sports league or competitive league.
-
B.
domesticLeagueOrganizer
chosen
Indicates that an entity is responsible for organizing or administering a domestic sports league.
-
C.
organizesProfessionalLeagues
Indicates that an entity is responsible for arranging, managing, and overseeing professional sports or competitive leagues for another entity.
-
D.
leagueStructure
Indicates how a league is organized, including its divisions, tiers, and the relationships or hierarchy between its constituent groups or competitions.
-
E.
league
Indicates that an organization or team participates in, is a member of, or is associated with a particular sports or competitive league.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 22, 2026, 8:47 a.m.