Triple
T10185025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympic Games baseball tournament |
E236884
|
entity |
| Predicate | eliminationFormatUsed |
P92587
|
FINISHED |
| Object | round-robin and knockout stages |
—
|
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: round-robin and knockout stages | Statement: [Olympic Games baseball tournament, eliminationFormatUsed, round-robin and knockout stages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eliminationFormatUsed Context triple: [Olympic Games baseball tournament, eliminationFormatUsed, round-robin and knockout stages]
-
A.
excludesFormat
Indicates that one entity explicitly disallows or omits a particular format from the set of acceptable or supported formats in a given context.
-
B.
selectionFormat
Indicates the specific structure or style in which a selection or choice is represented or presented.
-
C.
standardFormUsedIn
Indicates that a particular standard form is employed or applied within a given context, process, or system.
-
D.
includeFormat
Indicates that one entity contains or specifies the format or representation type of another entity.
-
E.
draftFormatUsed
Indicates that a particular draft was created or prepared using a specified format.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded36e9808190b385c5aec4889e00 |
completed | April 2, 2026, 4:14 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69cd7edc6cf081909d95859d880a4059 |
completed | April 1, 2026, 8:23 p.m. |
Created at: March 30, 2026, 9:12 p.m.