Triple

T15349205
Position Surface form Disambiguated ID Type / Status
Subject CITY E367005 entity
Predicate usedBySubsidiaryType P54892 FINISHED
Object regional subsidiary 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: regional subsidiary | Statement: [CITY, usedBySubsidiaryType, regional subsidiary]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedBySubsidiaryType
Context triple: [CITY, usedBySubsidiaryType, regional subsidiary]
  • A. usedBySubsidiaryOf chosen
    Indicates that something is used by an entity that is a subsidiary of another organization.
  • B. subsidiaryOrAsset
    Indicates that one entity is owned, controlled, or held as a subsidiary company or asset by another entity.
  • C. hasSubsidiaryLabel
    Indicates that one entity is identified as a subsidiary or subordinate organization of another entity.
  • D. usedByParentCompany
    Indicates that something (such as a resource, product, or service) is utilized or employed by a parent company in relation to its operations or activities.
  • E. coreSubsidiaryOf
    Indicates that one entity is a primary or central subsidiary that is owned or controlled by another entity.
  • 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_69d85a1355608190a6673ddb67231d54 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03e27f8a88190a0f65756e3a1fdfc completed April 16, 2026, 1:40 a.m.
PD Predicate disambiguation batch_69deca991e5081908b0df3d1ee7d5338 completed April 14, 2026, 11:15 p.m.
Created at: April 10, 2026, 3:17 a.m.