Triple
T24675338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000 Rugby League World Cup |
E610967
|
entity |
| Predicate | primaryHostRegion |
P150763
|
FINISHED |
| Object | United Kingdom |
—
|
NE NERFINISHED |
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: United Kingdom | Statement: [2000 Rugby League World Cup, primaryHostRegion, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryHostRegion Context triple: [2000 Rugby League World Cup, primaryHostRegion, United Kingdom]
-
A.
mainHostRegion
chosen
Indicates the primary geographic or network region in which a host or hosting environment is located or operates.
-
B.
primaryRegionDepicted
Indicates that a resource primarily depicts or visually represents a particular geographic or spatial region as its main subject.
-
C.
typicalHostRegion
Indicates the geographic region where a host is most commonly or characteristically found or associated.
-
D.
primaryRegionOfPopularity
Indicates the geographic region where something is most widely used, favored, or popular compared to other regions.
-
E.
primaryLongHaulRegion
Indicates the main long-distance geographic region in which an entity primarily operates or is associated for long-haul activities.
- 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_69e2c4d5c2dc8190ac857dea25ec6ce9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 3:03 a.m.