Triple
T29861511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pro14 |
E758329
|
entity |
| Predicate | notableWelshTeams |
P207186
|
FINISHED |
| Object | Ospreys |
E106003
|
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: Ospreys | Statement: [Pro14, notableWelshTeams, Ospreys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWelshTeams Context triple: [Pro14, notableWelshTeams, Ospreys]
-
A.
notableTeams
Indicates that there is a noteworthy association between an entity and one or more teams with which it is significantly connected or recognized.
-
B.
notableChampionTeam
Indicates that a team is notably recognized as the champion associated with a particular competition, event, or context.
-
C.
scottishTeam
Indicates that the team is associated with or originates from Scotland.
-
D.
notableTeamType
Indicates that an entity is notably associated with a team of a specified type (e.g., national team, club team, or other team category).
-
E.
notableInternationalTeam
Indicates that an entity is significantly recognized or distinguished at the international level within a team context.
- F. None of above. chosen
Provenance (5 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a271407abdc8190be8c16057fbd0838 |
completed | June 8, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 5:49 p.m.