Triple
T26116736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-EuroLeague First Team |
E658841
|
entity |
| Predicate | selectionAnnouncement |
P76290
|
FINISHED |
| Object | end of EuroLeague season |
—
|
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: end of EuroLeague season | Statement: [All-EuroLeague First Team, selectionAnnouncement, end of EuroLeague season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionAnnouncement Context triple: [All-EuroLeague First Team, selectionAnnouncement, end of EuroLeague season]
-
A.
selectionDescribedIn
Indicates that a particular selection or choice is documented, explained, or detailed within a specified description or source.
-
B.
selectedAt
Indicates that an entity was chosen or picked at a specific point in time or under particular selection conditions.
-
C.
announcedFor
chosen
Indicates that one entity has been publicly declared or made known in connection with, or on behalf of, another entity.
-
D.
announcedThat
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
-
E.
announcedTo
Indicates that one entity formally communicated or made known some information, decision, or event to another specific 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_69ee5bc20298819099a42be042eb2349 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 26, 2026, 8:05 p.m.