Triple

T35613710
Position Surface form Disambiguated ID Type / Status
Subject UNDCO E1029106 entity
Predicate hasOfficeAtLevel P146134 FINISHED
Object global level 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: global level | Statement: [UNDCO, hasOfficeAtLevel, global level]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOfficeAtLevel
Context triple: [UNDCO, hasOfficeAtLevel, global level]
  • A. hasOffice
    Indicates that an entity possesses or maintains an office at a particular location or within a specific organization.
  • B. notableOfficeLevel chosen
    Indicates that an entity holds or is associated with a notable office or position at a specified hierarchical level.
  • C. hasAssociatedOffice
    Indicates that an entity is linked to or connected with a particular office in an official or functional capacity.
  • D. servesAsOfficeOf
    Indicates that one entity functions as the official office, headquarters, or administrative base for another entity.
  • E. headquartersOfOffice
    Indicates that a particular location serves as the main headquarters for a specified office or organizational unit.
  • 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_69f76e0709408190bbe322bf1707ef6b completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fbad1e94988190b86d447a68e65067 completed May 6, 2026, 9:05 p.m.
PD Predicate disambiguation batch_69fba881b8e0819094790935152b99a1 completed May 6, 2026, 8:45 p.m.
Created at: May 3, 2026, 4:05 p.m.