Triple
T15434272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Van de Graaff generator |
E369717
|
entity |
| Predicate | effectOnPerson |
P75607
|
FINISHED |
| Object | can make hair stand on end |
—
|
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: can make hair stand on end | Statement: [Van de Graaff generator, effectOnPerson, can make hair stand on end]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnPerson Context triple: [Van de Graaff generator, effectOnPerson, can make hair stand on end]
-
A.
effectOnUser
chosen
Indicates how an action, event, or condition influences or impacts a user.
-
B.
effectOnOthers
Indicates the impact or influence that one entity’s actions, presence, or state has on other entities.
-
C.
affectedPerson
Indicates that a particular person is impacted or influenced by an event, action, or condition.
-
D.
effectOnSystem
Indicates the influence, change, or impact that one entity, action, or condition has on the state or behavior of a system.
-
E.
eventEffect
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03edb3ec481908b26164d4470c9bc |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.