Triple

T79805
Position Surface form Disambiguated ID Type / Status
Subject Brownian motion E1601 entity
Predicate generalization P2372 FINISHED
Object multi-dimensional Brownian motion 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: multi-dimensional Brownian motion | Statement: [Brownian motion, generalization, multi-dimensional Brownian motion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: generalization
Context triple: [Brownian motion, generalization, multi-dimensional Brownian motion]
  • A. generalizationOf chosen
    Indicates that one entity represents a broader, more general concept or category that subsumes or abstracts over another, more specific entity.
  • B. category
    Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
  • C. adaptation
    Indicates a relationship where one entity changes or is modified to better suit, function within, or correspond to another entity or context.
  • D. traction
    Indicates the degree to which one entity’s movement or influence effectively grips, pulls, or gains momentum relative to another entity or medium.
  • E. phenomenon
    Indicates that an entity is a perceptible event, occurrence, or process that can be observed or experienced.
  • 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_69a24c60d19c8190a1b6c105ca59ef5b completed Feb. 28, 2026, 2:01 a.m.
NER Named-entity recognition batch_69a24fd16c248190a6ee4cd96c388772 completed Feb. 28, 2026, 2:15 a.m.
PD Predicate disambiguation batch_69a24eb126b48190b410b859c1be99aa completed Feb. 28, 2026, 2:10 a.m.
Created at: Feb. 28, 2026, 2:06 a.m.