Triple
T27756387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Full Tilt! Pinball |
E701343
|
entity |
| Predicate | notableTable |
P7734
|
FINISHED |
| Object | Space Cadet |
—
|
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 | Statement: [Full Tilt! Pinball, notableTable, Space Cadet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTable Context triple: [Full Tilt! Pinball, notableTable, Space Cadet]
-
A.
notableDisplay
Indicates that something is prominently or distinctively presented in a way that draws special attention or recognition.
-
B.
notableTree
Indicates that a tree holds special significance or prominence, such as historical, cultural, ecological, or aesthetic importance, distinguishing it from ordinary trees.
-
C.
notableBoard
Indicates that an entity serves on, or is significantly associated with, a board that is notable or of particular importance.
-
D.
notableMap
Indicates that there is a map which is especially significant, well-known, or noteworthy in relation to the subject.
-
E.
notableElement
chosen
Indicates that an entity has a component, feature, or part that is especially significant, prominent, or noteworthy in relation to it.
- 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_6a0027e4a59481909417b2531daaf480 |
completed | May 10, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_6a0026a42bc08190ad3322ce625a523a |
completed | May 10, 2026, 6:33 a.m. |
Created at: April 27, 2026, 4:23 p.m.