Triple

T24882636
Position Surface form Disambiguated ID Type / Status
Subject Portland Course E622752 entity
Predicate lengthComparison P50260 FINISHED
Object shorter than the Championship Course at Royal Troon 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: shorter than the Championship Course at Royal Troon | Statement: [Portland Course, lengthComparison, shorter than the Championship Course at Royal Troon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lengthComparison
Context triple: [Portland Course, lengthComparison, shorter than the Championship Course at Royal Troon]
  • A. length
    Indicates a measurement relationship where a value specifies how long something is from one end to the other.
  • B. lengthClass
    Indicates a classification relationship where an entity is assigned to a category based on its length.
  • C. usesMatchLength
    Indicates that one entity applies or enforces the same length or duration as that of a corresponding match or matching element.
  • D. relativeLength chosen
    Indicates a comparative relationship between entities based on how long they are relative to one another.
  • E. rankByLength
    Indicates ordering a set of items based on their length, typically from shortest to longest or vice versa.
  • 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_69e2fac4aa848190b3446a3922cec150 completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f43043512481909501a3979cac9947 completed May 1, 2026, 4:46 a.m.
PD Predicate disambiguation batch_69f420fd375c81908ea4a4e60b76ee8f completed May 1, 2026, 3:41 a.m.
Created at: April 18, 2026, 5:24 a.m.