Triple
T24915161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ireland women's national rugby union team |
E623962
|
entity |
| Predicate | defeatedInTournament |
P50939
|
FINISHED |
| Object | 2014 Women's Rugby World Cup |
—
|
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: 2014 Women's Rugby World Cup | Statement: [Ireland women's national rugby union team, defeatedInTournament, 2014 Women's Rugby World Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defeatedInTournament Context triple: [Ireland women's national rugby union team, defeatedInTournament, 2014 Women's Rugby World Cup]
-
A.
defeatedInEvent
chosen
Indicates that one entity lost to another entity in the context of a specific event or competition.
-
B.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
-
C.
defeatedInBoutType
Indicates that one entity lost to another in a competitive match of a specified bout type or ruleset.
-
D.
wonTournament
Indicates that an entity emerged as the overall victor in a tournament competition.
-
E.
hasNotWonTournament
Indicates that an entity has not achieved victory in a specified tournament.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f4238b91d48190903e57456184af61 |
completed | May 1, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:28 a.m.