Triple
T2378911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Isles rugby union team |
E46264
|
entity |
| Predicate | playsMatchType |
P10212
|
FINISHED |
| Object | test matches |
—
|
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: test matches | Statement: [British Isles rugby union team, playsMatchType, test matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsMatchType Context triple: [British Isles rugby union team, playsMatchType, test matches]
-
A.
playType
Indicates the specific category or style of play or performance associated with an event or action.
-
B.
matchType
chosen
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
C.
playedSeasonType
Indicates that an entity participated in or was involved with a particular type of season (e.g., regular season, playoffs, preseason) within a competition or schedule.
-
D.
finalMatchType
Indicates the specific category or format of the concluding or decisive match in a series or competition.
-
E.
decidingMatchFor
Indicates a relationship where one entity is chosen or determined as the appropriate or final match for another entity among possible alternatives.
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc7974aa481908799ef2f854d1c9d |
completed | March 7, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69abc59f73f08190924a36d7d475d8f4 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.