Triple
T36717726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbarian F.C. Women |
E906958
|
entity |
| Predicate | firstMatchOpponent |
P8304
|
FINISHED |
| Object | Munster Women |
E623963
|
NE FINISHED |
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: Munster Women | Statement: [Barbarian F.C. Women, firstMatchOpponent, Munster Women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMatchOpponent Context triple: [Barbarian F.C. Women, firstMatchOpponent, Munster Women]
-
A.
firstRoundOpponent
Indicates that one entity is the opponent another entity faces in the first round of a competition or tournament.
-
B.
firstGameOpponent
chosen
Indicates that one entity is the opponent faced by another entity in its first game or match.
-
C.
finalLeagueMatchOpponent
Indicates the opposing team or player faced in an entity’s final league match.
-
D.
finalOpponentOf
Indicates that one entity serves as the last or ultimate opponent faced by another entity in a sequence of confrontations or competitions.
-
E.
firstMatchCompetition
Indicates that the referenced competition is the first one in which the entities faced each other or were matched against one another.
- F. None of above.
Provenance (4 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a383578748190b64fa169172c6a90 |
completed | June 23, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.