Triple

T28948150
Position Surface form Disambiguated ID Type / Status
Subject 稲城市 E730934 entity
Predicate 自治体コード P84232 FINISHED
Object 13225 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: 13225 | Statement: [稲城市, 自治体コード, 13225]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: 自治体コード
Context triple: [稲城市, 自治体コード, 13225]
  • A. hasPrefecturalCode
    Indicates that an entity is associated with a specific prefectural identification code assigned by an administrative system.
  • B. municipalCodeSystem
    Indicates a system that defines, organizes, or standardizes codes or regulations used by a municipality.
  • C. districtCode
    Indicates that an entity is associated with, or identified by, a specific administrative district code.
  • D. hasLocalGovernmentCode chosen
    Indicates that an entity is associated with a specific code assigned by a local government authority for identification or administrative purposes.
  • E. 都道府県
    Indicates a relationship where an entity is a Japanese prefecture or belongs to/pertains to a specific Japanese prefecture.
  • 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_69f043eb9bcc819091ac7b07aecb6475 completed April 28, 2026, 5:21 a.m.
NER Named-entity recognition batch_69f65b8a9a6c819091b9ec4563704490 completed May 2, 2026, 8:16 p.m.
PD Predicate disambiguation batch_69f659d02f1c8190831758ac52bb54e4 completed May 2, 2026, 8:08 p.m.
Created at: April 28, 2026, 8:42 a.m.