Triple

T16200432
Position Surface form Disambiguated ID Type / Status
Subject Amor group E393182 entity
Predicate hasDynamicalDefinitionSource P63525 FINISHED
Object IAU and planetary dynamics literature 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: IAU and planetary dynamics literature | Statement: [Amor group, hasDynamicalDefinitionSource, IAU and planetary dynamics literature]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDynamicalDefinitionSource
Context triple: [Amor group, hasDynamicalDefinitionSource, IAU and planetary dynamics literature]
  • A. hasDefinitionSource chosen
    Indicates that the definition of an entity originates from or is documented in a specified source.
  • B. hasDynamicalClass
    Indicates that an entity belongs to a specific category defined by its dynamical or motion-related behavior (e.g., orbital or kinematic characteristics).
  • C. isPartOfDynamically
    Indicates that one entity is currently a component or member of another entity in a way that can change over time or at runtime.
  • D. hasDefinition
    Indicates that one entity provides the meaning, explanation, or definition of another entity.
  • E. hasDynamics
    Indicates that one entity exhibits or is characterized by specific dynamic behavior, changes, or variations over time in relation to another entity or context.
  • 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_69d87f1f5bd08190bd01cac0d5b9d2ef completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e22709b0d88190b40787e0520d02ab completed April 17, 2026, 12:26 p.m.
PD Predicate disambiguation batch_69e219e11f6081909106b1240a17fd37 completed April 17, 2026, 11:30 a.m.
Created at: April 10, 2026, 5:03 a.m.