Triple
T9580291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canterbury rugby union team |
E231151
|
entity |
| Predicate | homeGroundUsedFor |
P89922
|
FINISHED |
| Object | rugby union |
—
|
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: rugby union | Statement: [Canterbury rugby union team, homeGroundUsedFor, rugby union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeGroundUsedFor Context triple: [Canterbury rugby union team, homeGroundUsedFor, rugby union]
-
A.
homeGroundType
Indicates the type or category of venue that serves as an entity’s designated home ground.
-
B.
homeGroundFeature
Indicates that a particular feature or characteristic is associated with or defines the home ground of an entity.
-
C.
homeGroundContext
Indicates the relationship between a sports team and the venue or location that serves as its primary home ground within a given contextual setting.
-
D.
homeFieldSurface
Indicates the type of playing surface used at a team's home field or stadium.
-
E.
primaryHomeGroundNot
Indicates that the specified location is explicitly not the entity’s primary home ground.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99ca96a48190a6fbe88387be6883 |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:05 p.m.