Triple

T5882342
Position Surface form Disambiguated ID Type / Status
Subject Cyrillic Extended-A E130776 entity
Predicate neighboringBlockNext P67240 FINISHED
Object Supplemental Punctuation 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: Supplemental Punctuation | Statement: [Cyrillic Extended-A, neighboringBlockNext, Supplemental Punctuation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: neighboringBlockNext
Context triple: [Cyrillic Extended-A, neighboringBlockNext, Supplemental Punctuation]
  • A. neighboringSignNext
    Indicates that one sign is immediately adjacent to and follows another sign in a sequence or spatial arrangement.
  • B. adjacentPlaneNext
    Indicates that one plane is immediately next to another plane in space, sharing a common boundary or edge without any intervening planes.
  • C. neighboringPort
    Indicates that two ports are geographically close to each other, typically sharing a boundary or lying within a short distance along a coast or waterway.
  • D. innerNeighbor
    Indicates that one entity is directly adjacent to another entity on the inside or interior side of a boundary or structure.
  • E. neighboringRegion
    Indicates that two regions share a common boundary or are directly adjacent to each other geographically.
  • F. None of above. chosen

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_69c0085523688190bfd487479ce819e6 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c03fe07b7081909f8577ec3a9a1a8d completed March 22, 2026, 7:15 p.m.
PD Predicate disambiguation batch_69c0334bdc308190ad0d7199ab975588 completed March 22, 2026, 6:22 p.m.
PDg Predicate description generation batch_69c03fdf954c8190ae97a5c9ce40bdfa completed March 22, 2026, 7:15 p.m.
Created at: March 22, 2026, 3:57 p.m.