Triple
T27756393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Full Tilt! Pinball |
E701343
|
entity |
| Predicate | themeOfTable |
P25955
|
FINISHED |
| Object | Space Cadet is a space-themed table |
—
|
NE NERFINISHED |
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: Space Cadet is a space-themed table | Statement: [Full Tilt! Pinball, themeOfTable, Space Cadet is a space-themed table]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeOfTable Context triple: [Full Tilt! Pinball, themeOfTable, Space Cadet is a space-themed table]
-
A.
themeFor
chosen
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
B.
dataTheme
Indicates the primary subject area or thematic category that the associated data pertains to.
-
C.
theme
Indicates the entity that is the primary participant or content affected or characterized by an action, event, or state.
-
D.
themeInspiration
Indicates that one entity serves as the creative source or conceptual basis that inspires or shapes the theme expressed in another entity.
-
E.
themeTreatment
Indicates that a treatment is applied to, affects, or is directed toward a particular theme or subject.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 4:23 p.m.