Triple
T32123861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Baby |
E820446
|
entity |
| Predicate | intimidationFactor |
P173602
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Big Baby, intimidationFactor, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intimidationFactor Context triple: [Big Baby, intimidationFactor, high]
-
A.
IntimidatorType
Indicates that one entity acts as a source or type of intimidation toward another entity.
-
B.
usesIntimidationMethods
Indicates that an entity employs threats, coercion, or fear-based tactics to influence or control another entity.
-
C.
perceivedThreat
Indicates that one entity regards another entity or situation as potentially harmful, dangerous, or adverse.
-
D.
isIntense
Indicates that something exhibits a high degree of strength, force, or concentration in its quality, effect, or activity.
-
E.
threat
Indicates a relationship where one entity expresses or poses potential harm, danger, or negative consequences toward another entity.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b96a22d48190aba271c414a1d926 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:29 a.m.