Triple
T34139891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rwanda National Basketball League |
E875686
|
entity |
| Predicate | hasMatchLocation |
P194027
|
FINISHED |
| Object | Kigali |
—
|
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: Kigali | Statement: [Rwanda National Basketball League, hasMatchLocation, Kigali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMatchLocation Context triple: [Rwanda National Basketball League, hasMatchLocation, Kigali]
-
A.
hasMatch
Indicates that one entity corresponds to, aligns with, or is considered an equivalent or suitable counterpart to another entity.
-
B.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
C.
hasTermLocation
chosen
Indicates that a term or concept is associated with, or occurs at, a specific location.
-
D.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
E.
hasLocationFocus
Indicates that the primary emphasis or relevance of something is centered on a specific location or place.
- 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_69f349aaeef08190a20e72a3fdeb7052 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a017114e7148190b7479284c316443d |
completed | May 11, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_6a016eebd60481909212e2a49ef95fbe |
completed | May 11, 2026, 5:53 a.m. |
Created at: May 1, 2026, 1:53 a.m.