Triple
T6465107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medieval Times Dinner & Tournament |
E142213
|
entity |
| Predicate | showFormat |
P15144
|
FINISHED |
| Object | tournament between color-coded knights |
—
|
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: tournament between color-coded knights | Statement: [Medieval Times Dinner & Tournament, showFormat, tournament between color-coded knights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showFormat Context triple: [Medieval Times Dinner & Tournament, showFormat, tournament between color-coded knights]
-
A.
showType
chosen
Indicates the category or format in which something is presented or displayed (e.g., type of show, presentation, or display mode).
-
B.
includeFormat
Indicates that one entity contains or specifies the format or representation type of another entity.
-
C.
displayType
Indicates the manner or format in which something is presented, shown, or rendered.
-
D.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
E.
packageFormat
Indicates the format or type in which a package is structured, encoded, or delivered.
- 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06a10305081909521ee200cf70a30 |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:49 p.m.