Triple
T1171917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beanpot tournament |
E24930
|
entity |
| Predicate | hasBracketStage |
P11195
|
FINISHED |
| Object | semifinals |
—
|
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: semifinals | Statement: [Beanpot tournament, hasBracketStage, semifinals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBracketStage Context triple: [Beanpot tournament, hasBracketStage, semifinals]
-
A.
hasGroupStage
Indicates that an entity includes, participates in, or is associated with a specific group stage within a larger multi-stage structure or process.
-
B.
hasKnockoutStage
Indicates that an entity includes, reaches, or is associated with a knockout (elimination) stage in a competition or tournament.
-
C.
hasQualifyingRounds
Indicates that an event or competition includes preliminary qualifying rounds that participants must complete before advancing further.
-
D.
hasPreliminaryRounds
Indicates that an event, competition, or process includes one or more initial qualifying rounds before the main or final stage.
-
E.
hasBracket
chosen
Indicates that one entity possesses, includes, or is associated with a bracket component or structure.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bceb3f188190b8b767380fe5986f |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5656948190b0b1d5446ad06005 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.