Triple
T15385152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strobulb |
E367897
|
entity |
| Predicate | effectOnGhosts |
P118565
|
FINISHED |
| Object | stuns ghosts |
—
|
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: stuns ghosts | Statement: [Strobulb, effectOnGhosts, stuns ghosts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnGhosts Context triple: [Strobulb, effectOnGhosts, stuns ghosts]
-
A.
effectOnOthers
Indicates the impact or influence that one entity’s actions, presence, or state has on other entities.
-
B.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
-
C.
effectOnInside
Indicates a relationship where one entity produces a change, influence, or impact on the internal state or condition of another entity.
-
D.
hasGhostCharacter
Indicates that an entity includes, features, or is associated with a character that is a ghost.
-
E.
effectOnSystem
Indicates the influence, change, or impact that one entity, action, or condition has on the state or behavior of a system.
- F. None of above. chosen
Provenance (4 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e74ff70819094c1a85f51d6e228 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:19 a.m.