Triple

T26492462
Position Surface form Disambiguated ID Type / Status
Subject Principality of Béarn E669193 entity
Predicate hadDistinctiveFeature P18160 FINISHED
Object distinct legal traditions 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: distinct legal traditions | Statement: [Principality of Béarn, hadDistinctiveFeature, distinct legal traditions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadDistinctiveFeature
Context triple: [Principality of Béarn, hadDistinctiveFeature, distinct legal traditions]
  • A. hasDistinctFeature chosen
    Indicates that an entity possesses a specific characteristic or attribute that differentiates it from others.
  • B. notableSoundCharacteristic
    Indicates a distinctive or noteworthy quality of the sound produced or associated with an entity.
  • C. distinguishingTrait
    Indicates that a particular characteristic or feature uniquely differentiates one entity from another.
  • D. linguisticFeature
    Indicates a relationship where a linguistic property, pattern, or characteristic is attributed to or associated with a language-related entity (such as a word, phrase, or text).
  • E. hasLinguisticFeature
    Indicates that an entity possesses a particular linguistic property, trait, or characteristic.
  • 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_69eeb319007081909642b414b114b35a completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69f621fcea1481909b6f8b3af1ee6820 completed May 2, 2026, 4:10 p.m.
PD Predicate disambiguation batch_69f620debeb48190b7db395fb86cf8d9 completed May 2, 2026, 4:05 p.m.
Created at: April 27, 2026, 1:05 a.m.