Triple

T10156311
Position Surface form Disambiguated ID Type / Status
Subject Palmer Scholar E233784 entity
Predicate relativeRankRequirement P25564 FINISHED
Object top five percent 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: top five percent | Statement: [Palmer Scholar, relativeRankRequirement, top five percent]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relativeRankRequirement
Context triple: [Palmer Scholar, relativeRankRequirement, top five percent]
  • A. rankRestriction chosen
    Indicates a constraint or limit placed on the rank or hierarchical level that an entity may hold within a given system or structure.
  • B. eligibleRank
    Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
  • C. rankComparedTo
    Indicates the relative ordering or position of one entity in comparison to another based on a specified ranking criterion.
  • D. isRanked
    Indicates that an entity has been assigned a position or level within an ordered hierarchy or comparative list.
  • E. rankStatus
    Indicates the hierarchical level or position an entity holds within an ordered ranking or status system.
  • 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_69ca848e80748190b91d1e04d35512c7 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cdec3a5e7c819098b2f9ccbde7cf94 completed April 2, 2026, 4:10 a.m.
PD Predicate disambiguation batch_69cd4ba795808190acc9124c98c6e40f completed April 1, 2026, 4:45 p.m.
Created at: March 30, 2026, 9:09 p.m.