Triple

T31892334
Position Surface form Disambiguated ID Type / Status
Subject ISO 639-3 E814176 entity
Predicate includesRetiredCodes P203490 FINISHED
Object yes 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: yes | Statement: [ISO 639-3, includesRetiredCodes, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includesRetiredCodes
Context triple: [ISO 639-3, includesRetiredCodes, yes]
  • A. hasRetiredNumbersDisplay
    Indicates that an entity features a display or presentation of numbers that have been officially retired (such as jersey numbers).
  • B. hasNumberRetired
    Indicates that a person or entity has had their identifying number (such as a jersey or employee number) officially withdrawn from further use in recognition of their significance.
  • C. includesSpecialServiceCodes
    Indicates that an entity contains or makes use of one or more designated special service codes as part of its configuration, offering, or processing.
  • D. isOfficialCodeFor
    Indicates that one entity serves as the formally recognized or authorized code that designates or identifies another entity.
  • E. hasRetiredPlayersFrom
    Indicates that an entity has players who previously played for it and have since retired, originating from the specified source entity (e.g., team, league, or country).
  • 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_69f348ef817481908440e2250319bcc8 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_6a019037edbc8190bdaec436ac2fcec6 completed May 11, 2026, 8:15 a.m.
PD Predicate disambiguation batch_6a018fe05a34819080068f588b5ff80c completed May 11, 2026, 8:14 a.m.
PDg Predicate description generation batch_6a0190370290819096183e9fb7d32cff completed May 11, 2026, 8:15 a.m.
Created at: April 30, 2026, 11:58 p.m.