Triple

T26062301
Position Surface form Disambiguated ID Type / Status
Subject KO E657292 entity
Predicate operatorOfRepresentedLine P109321 FINISHED
Object Keio Corporation NE NERFINISHED

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: Keio Corporation | Statement: [KO, operatorOfRepresentedLine, Keio Corporation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: operatorOfRepresentedLine
Context triple: [KO, operatorOfRepresentedLine, Keio Corporation]
  • A. operatesOnLine
    Indicates that an entity conducts operations, services, or activities along a specific line or route.
  • B. associatedLineOperator chosen
    Indicates that an entity is linked to, managed by, or otherwise connected with a specific line operator.
  • C. definedLine
    Indicates that a specific line (such as a boundary, path, or reference line) has been formally established or specified within a given context.
  • D. associatedLine
    Indicates that one entity is linked or connected to a particular line (such as a line item, line of text, or line in a structure) with which it is contextually or functionally related.
  • E. lineOpeningOperator
    Indicates that an operator is responsible for initiating or opening a line, such as a production line, communication line, or service line.
  • 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_69ee5bbd788481909e22bd7153d0c037 completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69fbaebc8f2c8190b94f1b4a3ec92e8c completed May 6, 2026, 9:12 p.m.
PD Predicate disambiguation batch_69fbadf1e6008190a71bbd196ba06844 completed May 6, 2026, 9:09 p.m.
Created at: April 26, 2026, 7:19 p.m.