Triple
T17961240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Province |
E449085
|
entity |
| Predicate | usesGroundFor |
P129915
|
FINISHED |
| Object | domestic first-class 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: domestic first-class matches | Statement: [Western Province, usesGroundFor, domestic first-class matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGroundFor Context triple: [Western Province, usesGroundFor, domestic first-class matches]
-
A.
usesGroundSystem
Indicates that one entity operates, relies on, or interacts with a particular ground-based system to perform its functions or services.
-
B.
associatedWithGround
Indicates that an entity has a defined connection or relationship with the ground, such as contact, support, or reference.
-
C.
isGroundedIn
Indicates that something is based on, supported by, or justified through a particular source, foundation, or set of principles.
-
D.
hasGroundPressure
Indicates that an entity exerts a specific amount of pressure on the ground or surface it is in contact with.
-
E.
usesOnLand
Indicates that one entity employs or operates another entity specifically in a land-based context.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b132cc10819088526a0b4b098d69 |
completed | April 19, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:22 a.m.