Triple

T26100468
Position Surface form Disambiguated ID Type / Status
Subject Mexican telephone numbering plan E658384 entity
Predicate previouslyUsedOpenPlan P147859 FINISHED
Object true 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: true | Statement: [Mexican telephone numbering plan, previouslyUsedOpenPlan, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: previouslyUsedOpenPlan
Context triple: [Mexican telephone numbering plan, previouslyUsedOpenPlan, true]
  • A. previousBuildingUse
    Indicates that a building previously served a specified use or function before its current one.
  • B. openedAsRenovatedSpace
    Indicates that a place or facility has been reopened to the public specifically after undergoing renovation or refurbishment.
  • C. previouslyUsedSystem chosen
    Indicates that an entity made use of a particular system at some time in the past, prior to the current context or state.
  • D. homeVenueFormerUse
    Indicates that a venue previously served a particular function or hosted a specific type of activity before its current use.
  • E. openedWithBuilding
    Indicates that an opening event or access action to something (e.g., a facility, space, or structure) is performed using or via a specific building as the means or context.
  • 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_69ee5bc09c288190bc42a11972841383 completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69f71422adac8190a5ceb32dcf820833 completed May 3, 2026, 9:23 a.m.
PD Predicate disambiguation batch_69f712764d2c819081b64b27e5de4a13 completed May 3, 2026, 9:16 a.m.
Created at: April 26, 2026, 7:54 p.m.