Triple
T25439050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eoin Morgan |
E637451
|
entity |
| Predicate | playedLeague |
P129367
|
FINISHED |
| Object | The Hundred |
—
|
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: The Hundred | Statement: [Eoin Morgan, playedLeague, The Hundred]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedLeague Context triple: [Eoin Morgan, playedLeague, The Hundred]
-
A.
leaguePlayedIn
Indicates that a sports team or player has participated in competitions within a particular league.
-
B.
playedInLeagueThatBecame
Indicates that an entity participated in a sports league which later transformed into, merged into, or was rebranded as another specified league.
-
C.
leagueUsedFor
Indicates that a particular league is utilized as the context, setting, or organizing framework for some activity, event, or competition.
-
D.
presentedInLeague
chosen
Indicates that an entity (such as a team, player, or performance) is featured, participates, or is officially included within a particular league.
-
E.
hasProfessionalLeague
Indicates that an entity is associated with or participates in a recognized professional sports 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 2 p.m.