Triple
T16097514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeopardy! |
E390524
|
entity |
| Predicate | hasBoardLayout |
P10827
|
FINISHED |
| Object | 6 categories per round |
—
|
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: 6 categories per round | Statement: [Jeopardy!, hasBoardLayout, 6 categories per round]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoardLayout Context triple: [Jeopardy!, hasBoardLayout, 6 categories per round]
-
A.
hasBoardType
Indicates that an entity is associated with or uses a specific type or category of board.
-
B.
hasBoardComposition
Indicates that an entity has a specific structure or makeup of its governing board, such as the types or proportions of members who serve on it.
-
C.
hasBoardSize
Indicates that an entity is associated with a board whose dimensions or overall size are specified.
-
D.
hasLayout
chosen
Indicates that one entity defines or is associated with the structural arrangement or organization (layout) of another entity.
-
E.
usesBoardShape
Indicates that one entity employs or is designed to work with a particular board shape as part of its function or configuration.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6551a48190afb7e0c61e22b541 |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.