Triple
T10862302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LCS |
E256434
|
entity |
| Predicate | hasPrizePoolType |
P34912
|
FINISHED |
| Object | seasonal prize pool |
—
|
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: seasonal prize pool | Statement: [LCS, hasPrizePoolType, seasonal prize pool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrizePoolType Context triple: [LCS, hasPrizePoolType, seasonal prize pool]
-
A.
hasPoolType
Indicates that an entity’s swimming pool possesses a specific type or classification (e.g., indoor, outdoor, heated).
-
B.
prizePool
Indicates that a certain amount of rewards or funds is collectively available to be distributed among participants in an event, competition, or activity.
-
C.
prizeType
Indicates the specific category or kind of prize associated with an entity or event.
-
D.
prizeFundType
chosen
Indicates the type or category of a prize fund associated with an award, competition, or financial pool.
-
E.
hasWinnerType
Indicates that an entity has a specific type or category of winner associated with it.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7515238108190a72eb8cd147f223d |
completed | April 9, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.