Triple
T3841429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilmslow Rugby Club |
E93457
|
entity |
| Predicate | geographicScopeOfPlayers |
P6407
|
FINISHED |
| Object | Wilmslow area |
—
|
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: Wilmslow area | Statement: [Wilmslow Rugby Club, geographicScopeOfPlayers, Wilmslow area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicScopeOfPlayers Context triple: [Wilmslow Rugby Club, geographicScopeOfPlayers, Wilmslow area]
-
A.
participantsRegion
Indicates that the related entities are associated with, originate from, or operate within a specified geographic region.
-
B.
teamLocationScope
chosen
Indicates the geographic or organizational area within which a team operates or is considered relevant.
-
C.
geographicScopeOfIssuers
Indicates the geographic region or area in which the referenced issuers are located or operate.
-
D.
continentOfActivity
Indicates the continent on which an entity primarily operates, is active, or conducts its main activities.
-
E.
countryOfPlayer
Indicates the country with which a given player is associated, such as their nationality or the nation they represent.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeebb235088190b115623e54ea2ab1 |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.