Triple

T34304788
Position Surface form Disambiguated ID Type / Status
Subject Expo ’70 master plan E880276 entity
Predicate visitorCapacityPlanned P179734 FINISHED
Object tens of millions of visitors 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: tens of millions of visitors | Statement: [Expo ’70 master plan, visitorCapacityPlanned, tens of millions of visitors]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: visitorCapacityPlanned
Context triple: [Expo ’70 master plan, visitorCapacityPlanned, tens of millions of visitors]
  • A. visitorLimit
    Indicates a constraint specifying the maximum number of visitors allowed for a given entity or context.
  • B. officialCapacity
    Indicates that an action or relationship is undertaken or held by an entity in their formal, authorized, or institutional role rather than in a personal capacity.
  • C. stageCapacity
    Indicates the maximum number of people or amount of occupancy that a particular stage can accommodate.
  • D. roomCapacity
    Indicates the maximum number of people or occupants that a room is designed or allowed to hold.
  • E. typicalSeatingCapacityUpperBound
    Indicates the maximum number of seats that a venue or vehicle is typically designed or allowed to accommodate under normal conditions.
  • 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_69f349b79f6c81909cb468c92c39c74d completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f727bde8f88190ad746ca515134ca1 completed May 3, 2026, 10:47 a.m.
PD Predicate disambiguation batch_69f72739c30c81908642eef3feb3afcf completed May 3, 2026, 10:45 a.m.
PDg Predicate description generation batch_69f727bd39b081908457590c3ba9b745 completed May 3, 2026, 10:47 a.m.
Created at: May 1, 2026, 1:57 a.m.