Triple
T6408670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | League C |
E127651
|
entity |
| Predicate | usesGroupWinnersPromotion |
P70463
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [League C, usesGroupWinnersPromotion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGroupWinnersPromotion Context triple: [League C, usesGroupWinnersPromotion, true]
-
A.
hasPromotionFrom
Indicates that an entity receives or is associated with a promotion that originates from a specified source entity (such as a campaign, organization, or person).
-
B.
allowsPromotion
Indicates that one entity grants permission or enables another entity to be promoted to a higher status, level, or position.
-
C.
hasGrandPrize
Indicates that an entity possesses, is awarded, or is associated with a grand prize in a given context.
-
D.
winnerReceives
Indicates that the entity identified as the winner is granted or awarded the specified item, benefit, or outcome as a result of winning.
-
E.
hasMultipleWinnersPossible
Indicates that a situation, event, or contest allows for more than one winner to be recognized or selected.
- F. None of above. chosen
Provenance (4 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068cdf25881908d42a5d979637ad6 |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f40ecc8190b1df17b96767675c |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:41 p.m.