Triple

T38328604
Position Surface form Disambiguated ID Type / Status
Subject Diamond in the Desert E1036858 entity
Predicate plannedPostTournamentCapacity P109700 FINISHED
Object 20000 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: 20000 | Statement: [Diamond in the Desert, plannedPostTournamentCapacity, 20000]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: plannedPostTournamentCapacity
Context triple: [Diamond in the Desert, plannedPostTournamentCapacity, 20000]
  • A. postTournamentCapacityPlanned chosen
    Indicates that a planned capacity level is designated for an entity after the conclusion of a tournament.
  • B. postTournamentCapacity
    Indicates the capacity or size of something after a tournament has concluded.
  • C. capacityAfterTournament
    Indicates the resulting capacity of something after a tournament has taken place or been completed.
  • D. visitorCapacityPlanned
    Indicates the planned or intended maximum number of visitors that a place or event is designed to accommodate.
  • E. postOlympicsCapacity
    Indicates the seating or usage capacity of a venue after the Olympic Games have concluded.
  • 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_69f76e1c16fc8190bde982289dd5106b completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fd6a1c1c4881908090053bc359b181 completed May 8, 2026, 4:44 a.m.
PD Predicate disambiguation batch_69fd696f24d8819091033afacbdaadc5 completed May 8, 2026, 4:41 a.m.
Created at: May 3, 2026, 4:30 p.m.