Triple

T26034852
Position Surface form Disambiguated ID Type / Status
Subject Segré–Silberberg effect E647522 entity
Predicate governingForces P131424 FINISHED
Object hydrodynamic lift forces 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: hydrodynamic lift forces | Statement: [Segré–Silberberg effect, governingForces, hydrodynamic lift forces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: governingForces
Context triple: [Segré–Silberberg effect, governingForces, hydrodynamic lift forces]
  • A. governingForceOf chosen
    Indicates that one entity functions as the primary controlling or directing influence over another entity’s behavior, state, or dynamics.
  • B. natureOfForces
    Indicates the fundamental type or character of the forces involved in an interaction or system.
  • C. typeOfForcesDirected
    Indicates that certain forces are oriented or directed toward a particular target, direction, or reference.
  • D. componentForces
    Indicates that a force is decomposed into its constituent directional components that together produce the original overall force.
  • E. forces
    Indicates that one entity compels or obliges another entity to perform an action or be in a certain state, typically against the latter’s will or without full freedom of choice.
  • 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_69e77e8c88f08190858c4c81bd2e1b9a completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f7b5ccbda481908fe1945c35e36ce8 completed May 3, 2026, 8:53 p.m.
PD Predicate disambiguation batch_69f7b4c06f5881908f0b98cad6796478 completed May 3, 2026, 8:49 p.m.
Created at: April 22, 2026, 9:07 a.m.