Triple
T31453054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIH Pro League |
E802374
|
entity |
| Predicate | hasWomenCompetition |
P80775
|
FINISHED |
| Object | Women's FIH Pro 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: Women's FIH Pro League | Statement: [FIH Pro League, hasWomenCompetition, Women's FIH Pro League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWomenCompetition Context triple: [FIH Pro League, hasWomenCompetition, Women's FIH Pro League]
-
A.
hasFemaleCompetitors
Indicates that an entity participates in a competitive context where at least some of the competitors are female.
-
B.
hasWomenSeries
Indicates that an entity is associated with or includes a series specifically for women.
-
C.
hasWomenTeamInLeague
Indicates that an entity has a women’s team that participates in a specified league.
-
D.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
E.
includesWomen'sLeagues
chosen
Indicates that the subject entity encompasses, offers, or is associated with one or more leagues specifically organized for women.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: April 30, 2026, 9:14 p.m.