Triple

T25513122
Position Surface form Disambiguated ID Type / Status
Subject United States ZIP code system E639434 entity
Predicate specialAllocation P77513 FINISHED
Object military APO/FPO/DPO addresses 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: military APO/FPO/DPO addresses | Statement: [United States ZIP code system, specialAllocation, military APO/FPO/DPO addresses]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: specialAllocation
Context triple: [United States ZIP code system, specialAllocation, military APO/FPO/DPO addresses]
  • A. allocates
    Indicates the act of assigning or distributing resources, responsibilities, or portions of something to specific entities or purposes.
  • B. allocation
    Indicates the distribution or assignment of resources, responsibilities, or items among entities according to some rule or plan.
  • C. specialValue
    Indicates that an entity possesses a distinguished or exceptional value compared to typical or default values in the given context.
  • D. collectivelyAllocated
    Indicates that a resource or responsibility is assigned to a group as a whole rather than to individual members separately.
  • E. allocationType chosen
    Indicates the specific manner or category by which resources, responsibilities, or items are assigned or distributed among entities.
  • 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_69e75dbe32e48190a62d749a0ff2a96a completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f82fe30881909915c13a183be6c3 completed May 2, 2026, 1:12 p.m.
PD Predicate disambiguation batch_69f49377411c8190b2188de444d76795 completed May 1, 2026, 11:50 a.m.
Created at: April 21, 2026, 2:53 p.m.