Triple

T28061930
Position Surface form Disambiguated ID Type / Status
Subject Paris La Défense Arena E709133 entity
Predicate capacityForRugby P163659 FINISHED
Object approximately 30000 spectators 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: approximately 30000 spectators | Statement: [Paris La Défense Arena, capacityForRugby, approximately 30000 spectators]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: capacityForRugby
Context triple: [Paris La Défense Arena, capacityForRugby, approximately 30000 spectators]
  • A. capacityRugby chosen
    Indicates that an entity has a specified seating or attendance capacity for hosting rugby events or matches.
  • B. capacityForWorldCup
    Indicates the maximum number of spectators a venue can accommodate specifically for World Cup events.
  • C. playerCapacity
    Indicates the maximum number of players that can simultaneously participate in or be accommodated by something (such as a game, session, or venue).
  • D. codeOfRugby
    Indicates that one entity is the specific code or variant of rugby (e.g., rugby union, rugby league) under which the other entity is played, governed, or classified.
  • E. hasRugbyGround
    Indicates that an entity possesses, contains, or is associated with a rugby ground as a facility or location.
  • 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_69ef9b6eb6d88190a3fea236eb0f7bed completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69f640174f388190b2c018b39d8aeeac completed May 2, 2026, 6:19 p.m.
PD Predicate disambiguation batch_69f63c6a8474819091b8c6fe98e3862d completed May 2, 2026, 6:03 p.m.
Created at: April 27, 2026, 8:40 p.m.