Triple
T26924986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESL Pro League |
E677750
|
entity |
| Predicate | hasLANFinals |
P181211
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ESL Pro League, hasLANFinals, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLANFinals Context triple: [ESL Pro League, hasLANFinals, yes]
-
A.
isFinalsOf
Indicates that one entity represents the final or concluding stage, round, or version of another entity.
-
B.
hasFinale
Indicates that one entity serves as the concluding or final part (such as an ending segment, episode, or event) of another entity.
-
C.
hasFinalTournament
Indicates that an entity is associated with a specific tournament that serves as its final or concluding competition.
-
D.
hasLiveFinale
Indicates that an event, show, or series concludes with a final installment that is broadcast or performed live.
-
E.
hasNumberOfFinalists
Indicates the relationship between an entity and the count of finalists associated with it.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f76759b3c48190ad8f1b33596f98c4 |
completed | May 3, 2026, 3:18 p.m. |
Created at: April 27, 2026, 6:09 a.m.