Triple

T17978594
Position Surface form Disambiguated ID Type / Status
Subject Prunoideae E449540 entity
Predicate hasMemberTraditionally P11158 FINISHED
Object stone-fruit trees 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: stone-fruit trees | Statement: [Prunoideae, hasMemberTraditionally, stone-fruit trees]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMemberTraditionally
Context triple: [Prunoideae, hasMemberTraditionally, stone-fruit trees]
  • A. hasTraditionIn
    Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
  • B. isTraditionOf
    Indicates that something is a customary practice, belief, or ritual associated with or belonging to a particular group, culture, or context.
  • C. traditionallyOneOf chosen
    Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
  • D. hasTraditionalAssociation
    Indicates that one entity is customarily or historically linked with another according to tradition or long-established practice.
  • E. hasTribalMembers
    Indicates that a group, organization, or entity includes individuals who are recognized as members of a specific tribe.
  • 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_69d8b9f9927c8190a006110c8b996e61 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4b201d1508190a9d6abbfd04bdcae completed April 19, 2026, 10:44 a.m.
PD Predicate disambiguation batch_69e3f8fa62688190a5d5c361ab896256 completed April 18, 2026, 9:34 p.m.
Created at: April 10, 2026, 10:22 a.m.