Triple
T16625135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krusty Krab 2 |
E403924
|
entity |
| Predicate | hasOnScreenFunction |
P87539
|
FINISHED |
| Object | setting for SpongeBob’s Goofy Goober-fueled speech |
—
|
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: setting for SpongeBob’s Goofy Goober-fueled speech | Statement: [Krusty Krab 2, hasOnScreenFunction, setting for SpongeBob’s Goofy Goober-fueled speech]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnScreenFunction Context triple: [Krusty Krab 2, hasOnScreenFunction, setting for SpongeBob’s Goofy Goober-fueled speech]
-
A.
hasOnscreenFunction
chosen
Indicates that an entity serves a particular role or performs a specific function when it appears on screen.
-
B.
hasOnScreenDynamic
Indicates that one entity displays or presents another entity as a changing or interactive element on a screen.
-
C.
hasScreen
Indicates that an entity is equipped with or includes a screen or display component.
-
D.
hasTopScreenSize
Indicates that an entity (typically a device) possesses a top screen with a specified size or dimension.
-
E.
hasNumberOfScreens
Indicates the quantity of screens associated with or contained in a given entity.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37551cd888190becc21deba87980d |
completed | April 18, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.