Triple

T5453025
Position Surface form Disambiguated ID Type / Status
Subject Ram E122411 entity
Predicate usedMetaphoricallyFor P15665 FINISHED
Object forceful impact 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: forceful impact | Statement: [Ram, usedMetaphoricallyFor, forceful impact]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedMetaphoricallyFor
Context triple: [Ram, usedMetaphoricallyFor, forceful impact]
  • A. keyMetaphor
    Indicates that one entity functions as a central or primary metaphor used to conceptualize, explain, or structure understanding of another entity.
  • B. primaryMetaphor chosen
    Indicates a fundamental conceptual mapping where one domain (often concrete or physical) is systematically understood in terms of another (often abstract), forming a basic metaphorical relationship between them.
  • C. usedInformallyAlongside
    Indicates that something is employed in an informal, non-standard way together with or in addition to something else.
  • D. possibleMeaning
    Indicates that something may plausibly represent, signify, or be interpreted as a particular meaning or sense.
  • E. usedFor
    Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
  • 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_69bd46424248819085282ddf50a565f3 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd95be329c81908783420cf81b6af5 completed March 20, 2026, 6:45 p.m.
PD Predicate disambiguation batch_69bd919e8d18819098c4af6a015e5cc2 completed March 20, 2026, 6:27 p.m.
Created at: March 20, 2026, 2:08 p.m.