Triple

T30075275
Position Surface form Disambiguated ID Type / Status
Subject European peerage ranks E764300 entity
Predicate hasLowestCommonRank P191094 FINISHED
Object baron 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: baron | Statement: [European peerage ranks, hasLowestCommonRank, baron]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLowestCommonRank
Context triple: [European peerage ranks, hasLowestCommonRank, baron]
  • A. hasLowestTerminusAmong
    Indicates that one entity’s terminus (end point) is lower in position or elevation than the termini of all other compared entities.
  • B. containsRank
    Indicates that one entity includes or encompasses another entity that has a specific rank or hierarchical level within it.
  • C. hasComparableRank
    Indicates that two entities hold positions or levels that are equivalent or similar in rank within a given hierarchy or system.
  • D. isLowerReachOf
    Indicates that one entity represents the downstream or lower section of another entity’s continuous extent, such as along a river, channel, or similar linear feature.
  • E. lowestRank
    Indicates that the subject has the least or worst rank in an ordered set compared to all other related entities.
  • F. None of above. chosen

Provenance (4 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_69f22472eee081909791dc372aa766e9 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fcda3699948190adb57625bae08091 completed May 7, 2026, 6:30 p.m.
PD Predicate disambiguation batch_69fcd8fd16d08190b0aca6e19a632e99 completed May 7, 2026, 6:25 p.m.
PDg Predicate description generation batch_69fcda35dc048190a3c90e15230900e0 completed May 7, 2026, 6:30 p.m.
Created at: April 29, 2026, 7:01 p.m.