Triple
T28031641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willie Beamen |
E708284
|
entity |
| Predicate | playsForFictionalLeagueTeam |
P6404
|
FINISHED |
| Object | Miami Sharks |
—
|
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: Miami Sharks | Statement: [Willie Beamen, playsForFictionalLeagueTeam, Miami Sharks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsForFictionalLeagueTeam Context triple: [Willie Beamen, playsForFictionalLeagueTeam, Miami Sharks]
-
A.
fictionalTeam
Indicates that the related entities are members of, or otherwise associated with, the same fictional team within a narrative or imaginary context.
-
B.
leagueOfFictionalTeam
Indicates that a fictional sports team is a member of, or competes within, a particular sports league.
-
C.
playsForTitle
chosen
Indicates that an entity performs or competes on behalf of a team, organization, or group under a specific title or designation.
-
D.
fictionalLeague
Indicates that an entity is associated with or belongs to a league that exists only in fiction rather than in reality.
-
E.
ownsProfessionalTeam
Indicates that one entity has legal ownership or controlling interest in a professional sports team.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 8:17 p.m.