Triple
T33431712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pool B (2015 Rugby World Cup) |
E856146
|
entity |
| Predicate | featuredUpset |
P68011
|
FINISHED |
| Object | Japan’s victory over South Africa |
—
|
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: Japan’s victory over South Africa | Statement: [Pool B (2015 Rugby World Cup), featuredUpset, Japan’s victory over South Africa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredUpset Context triple: [Pool B (2015 Rugby World Cup), featuredUpset, Japan’s victory over South Africa]
-
A.
upset
Indicates that one entity causes another to feel distressed, unhappy, or emotionally disturbed.
-
B.
featuredFor
Indicates that one entity is highlighted, promoted, or specially showcased in the context or for the benefit of another entity.
-
C.
alsoFeatured
Indicates that an entity appears in addition to another primary entity within the same context, work, or presentation.
-
D.
featuredElement
chosen
Indicates that one element is highlighted or given special prominence relative to others in a given context.
-
E.
featuredIssue
Indicates that an issue is highlighted or given special prominence relative to other issues.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01b31b233c819091974a06f7a76d4a |
completed | May 11, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_6a01b2c147008190bbf9e0fa1bbae1f3 |
completed | May 11, 2026, 10:43 a.m. |
Created at: May 1, 2026, 1:36 a.m.