Triple
T16625125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krusty Krab 2 |
E403924
|
entity |
| Predicate | plotConnection |
P2762
|
FINISHED |
| Object | linked to Mr. Krabs’ promotion decision |
—
|
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: linked to Mr. Krabs’ promotion decision | Statement: [Krusty Krab 2, plotConnection, linked to Mr. Krabs’ promotion decision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plotConnection Context triple: [Krusty Krab 2, plotConnection, linked to Mr. Krabs’ promotion decision]
-
A.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
-
B.
plotElement
chosen
Indicates that one entity functions as a narrative component or structural element within the storyline of another entity (such as a work of fiction or media).
-
C.
loreConnection
Indicates a relationship where two entities are linked through shared story, background, or world-building context within a fictional or narrative universe.
-
D.
connectsCitiesViaLine
Indicates a relationship where a transportation line directly links two or more cities.
-
E.
connectionTo
Indicates a relationship in which one entity is linked, associated, or otherwise related to another 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.