Triple
T37961822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiny Tina |
E947024
|
entity |
| Predicate | spinOffGame |
P29865
|
FINISHED |
| Object | Tiny Tina’s Wonderlands |
—
|
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: Tiny Tina’s Wonderlands | Statement: [Tiny Tina, spinOffGame, Tiny Tina’s Wonderlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spinOffGame Context triple: [Tiny Tina, spinOffGame, Tiny Tina’s Wonderlands]
-
A.
spinOff
Indicates that a new entity is created by separating or divesting part of an existing entity, forming an independent offshoot derived from the original.
-
B.
spinOffPlatform
Indicates that one platform has been created or derived as a spin-off from another platform.
-
C.
spinOffNetwork
Indicates that a new network entity has been created as a derivative or offshoot of an existing network.
-
D.
spinOffRole
Indicates that one role or position has been derived or created as a secondary or offshoot role from another original role.
-
E.
spinoffSetting
chosen
Indicates that one work is set in a narrative world or environment derived from, but distinct from, the setting of another work.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.