Triple
T33347629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pool of Death (2015 Rugby World Cup) |
E853842
|
entity |
| Predicate | containedTeam |
P29737
|
FINISHED |
| Object | England national rugby union team |
—
|
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: England national rugby union team | Statement: [Pool of Death (2015 Rugby World Cup), containedTeam, England national rugby union team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containedTeam Context triple: [Pool of Death (2015 Rugby World Cup), containedTeam, England national rugby union team]
-
A.
associatedTeam
Indicates that one entity is linked or connected to a particular team, typically as its member, owner, or primary affiliation.
-
B.
includesTeam
chosen
Indicates that a group, project, or organization has a specific team as one of its constituent members or components.
-
C.
memberTeam
Indicates that an entity belongs to or is part of a specific team.
-
D.
hasTeamFor
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
-
E.
includesTeamsThat
Indicates that an entity contains or encompasses specific teams as part of its composition or scope.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0019b0e9fc81909494320f05e81742 |
completed | May 10, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a00193379e0819096d1985686ce10e3 |
completed | May 10, 2026, 5:35 a.m. |
Created at: May 1, 2026, 1:34 a.m.