Triple
T9357682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Professor Westervelt |
E225183
|
entity |
| Predicate | exerts |
P69578
|
FINISHED |
| Object | psychological dominance over others |
—
|
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: psychological dominance over others | Statement: [Professor Westervelt, exerts, psychological dominance over others]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exerts Context triple: [Professor Westervelt, exerts, psychological dominance over others]
-
A.
expresses
Indicates that one entity conveys, communicates, or articulates a thought, feeling, or idea through another medium or form.
-
B.
expel
Indicates forcing an entity to leave or be removed from a place, group, or situation, typically as a punishment or consequence.
-
C.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
D.
exercisedPowerFrom
chosen
Indicates that one entity exerted authority, control, or influence originating from a particular source, position, or location over another entity or context.
-
E.
imposes
Indicates that one entity enforces, applies, or places a rule, condition, burden, or obligation upon 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_69ca842bdd648190904131d58620d448 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4ff06608819086e9f11789beaf22 |
completed | April 1, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69cc7a68ab9481909f97cb70764697cc |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:42 p.m.