Triple
T36264403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglo-Welsh Cup |
E892181
|
entity |
| Predicate | restructuredAsAngloWelsh |
P184824
|
FINISHED |
| Object | 2005 |
—
|
LITERAL 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: 2005 | Statement: [Anglo-Welsh Cup, restructuredAsAngloWelsh, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restructuredAsAngloWelsh Context triple: [Anglo-Welsh Cup, restructuredAsAngloWelsh, 2005]
-
A.
replacedInWalesBy
Indicates that something previously in use or effect in Wales has been superseded or substituted by another specific thing.
-
B.
returnedToWelshSystem
Indicates that an entity has gone back into the Welsh system after having been outside it (e.g., returning to a Welsh institution, framework, or jurisdiction).
-
C.
englandTries
Indicates that England makes an attempt to perform or achieve a particular action or outcome.
-
D.
rebrandedAsUnitedRugbyChampionship
Indicates that an entity has changed its name or brand identity to become the United Rugby Championship.
-
E.
historicallyAnglicisedDuring
Indicates that an entity’s name or form was historically rendered into an Anglicised version during a specified time period.
- F. None of above. chosen
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_69f76e4699188190af045b11a840ce31 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b625b090819095a9db9382211af7 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b57aa0848190a22c31c3ff90e0ab |
completed | May 3, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:09 p.m.