Triple
T36654067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rugby Africa Bronze Cup |
E904941
|
entity |
| Predicate | competitionHierarchy |
P43092
|
FINISHED |
| Object | below Rugby Africa Silver Cup |
—
|
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: below Rugby Africa Silver Cup | Statement: [Rugby Africa Bronze Cup, competitionHierarchy, below Rugby Africa Silver Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionHierarchy Context triple: [Rugby Africa Bronze Cup, competitionHierarchy, below Rugby Africa Silver Cup]
-
A.
competitionHierarchyLevel
chosen
Indicates the relative rank or tier of a competition within an overall competitive structure or hierarchy.
-
B.
competitionLevel
Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
-
C.
competitionLevelOf
Indicates the degree or intensity of competitiveness associated with an entity, event, or context.
-
D.
competitionWeight
Indicates the weight or importance assigned to an entity within a competitive context or event.
-
E.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 3, 2026, 4:11 p.m.