Triple

T33990111
Position Surface form Disambiguated ID Type / Status
Subject Moscow airports E871517 entity
Predicate hasCollectiveCode P48550 FINISHED
Object MOW E984135 NE 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: MOW | Statement: [Moscow airports, hasCollectiveCode, MOW]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCollectiveCode
Context triple: [Moscow airports, hasCollectiveCode, MOW]
  • A. isCollectiveCodeFor
    Indicates that one term or label serves as an umbrella or group designation that collectively refers to multiple distinct items or concepts.
  • B. hasCollectiveCharacter
    Indicates that a group or set of entities is treated as a unified whole, sharing a collective nature or identity rather than being considered solely as separate individuals.
  • C. isCollectiveIdentityOf
    Indicates that one entity functions as the shared or group-level identity that represents or encompasses another entity or set of entities.
  • D. collectionCode chosen
    Indicates the specific identifier or code assigned to the collection to which an item or resource belongs.
  • E. hasCollaborativeGroup
    Indicates that an entity participates in or is associated with a collaborative group formed to work together toward shared goals or activities.
  • F. None of above.

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_69f3499e964c8190b674b03f6f791b4b completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_6a037c8ae0248190b7e2ce4bf852c22d completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a36a023877c8190bd2525282af9629d completed June 20, 2026, 2:13 p.m.
PD Predicate disambiguation batch_6a0379f963908190846d232f386fd98f completed May 12, 2026, 7:05 p.m.
Created at: May 1, 2026, 1:50 a.m.