Triple
T24469456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winning Alliance |
E617058
|
entity |
| Predicate | isOftenMentionedAs |
P21265
|
FINISHED |
| Object | event champion alliance |
—
|
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: event champion alliance | Statement: [Winning Alliance, isOftenMentionedAs, event champion alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenMentionedAs Context triple: [Winning Alliance, isOftenMentionedAs, event champion alliance]
-
A.
isFrequentlyIncludedIn
Indicates that something is regularly or commonly contained or made part of something else.
-
B.
mentionedAs
Indicates that one entity is referred to or cited by name or description in the context of another entity.
-
C.
frequentlyDiscussedIn
Indicates that a topic, subject, or entity is often the focus of conversation, debate, or mention within a particular context or medium.
-
D.
mentionedWith
Indicates that two entities are mentioned together or in close association within the same context, such as a document, sentence, or conversation.
-
E.
isFrequentlyDescribedAs
chosen
Indicates that something is often characterized or referred to using a particular description or set of attributes.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f299422cdc8190bc8d56243b7bc313 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:20 a.m.