Triple

T24971167
Position Surface form Disambiguated ID Type / Status
Subject Court Simonne-Mathieu E624892 entity
Predicate rankingWithinComplex P59486 FINISHED
Object one of the main show courts at Roland Garros 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: one of the main show courts at Roland Garros | Statement: [Court Simonne-Mathieu, rankingWithinComplex, one of the main show courts at Roland Garros]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rankingWithinComplex
Context triple: [Court Simonne-Mathieu, rankingWithinComplex, one of the main show courts at Roland Garros]
  • A. rankingScope chosen
    Indicates the context or domain within which a ranking is defined, interpreted, or applied.
  • B. rankComparedTo
    Indicates the relative ordering or position of one entity in comparison to another based on a specified ranking criterion.
  • C. rankIn
    Indicates the relative position or level an entity holds within an ordered set, hierarchy, or competitive context.
  • D. rankingBehind
    Indicates that one entity holds a lower or later position than another in an ordered ranking or hierarchy.
  • E. depthRank
    Indicates the relative ordering of entities based on how deep or distant they are along a specified depth dimension or hierarchy.
  • 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_69e2ff24512481908e9a72315b8d0354 completed April 18, 2026, 3:48 a.m.
NER Named-entity recognition batch_69f62d89b89c8190afb372a8172111e7 completed May 2, 2026, 4:59 p.m.
PD Predicate disambiguation batch_69f62c1379f08190836c3e02b0c892df completed May 2, 2026, 4:53 p.m.
Created at: April 18, 2026, 6:01 a.m.