Triple
T14288919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wales women's national rugby union team |
E354255
|
entity |
| Predicate | governedSince |
P45811
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Wales women's national rugby union team, governedSince, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedSince Context triple: [Wales women's national rugby union team, governedSince, 1990s]
-
A.
governingSince
chosen
Indicates that one entity has held a governing or ruling role over another entity starting from a specified point in time.
-
B.
laterGovernedAs
Indicates that an entity subsequently held governing authority over another entity at a later time.
-
C.
governedDuringPeriod
Indicates that a governing entity exercised authority or control over another entity throughout a specified time period.
-
D.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
E.
governedFrom
Indicates that an entity exercises governing authority or administrative control over another entity from a specific location or seat of power.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de698023288190b1d705235c2b2ca3 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:11 a.m.