Triple

T35804171
Position Surface form Disambiguated ID Type / Status
Subject 金鯱 E1035061 entity
Predicate 所在(一般) P80176 FINISHED
Object 天守の屋根上に据えられる 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: 天守の屋根上に据えられる | Statement: [金鯱, 所在(一般), 天守の屋根上に据えられる]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: 所在(一般)
Context triple: [金鯱, 所在(一般), 天守の屋根上に据えられる]
  • A. 定位 chosen
    Indicates the act of determining or establishing the position, location, or placement of one entity relative to a reference point or context.
  • B. 所在都市
    Indicates the city in which an entity is located or based.
  • C. likelyLocatedIn
    Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
  • D. sometimesLocatedIn
    Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
  • E. 通過場所
    Indicates that an entity moves through, passes by, or traverses a particular place or location.
  • 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_69f76e169bd081909f16cd8c9ee7870c completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a283388c81908e4a9ee3369e8d6f completed May 3, 2026, 7:31 p.m.
PD Predicate disambiguation batch_69f7a070e23881909a233370acb57384 completed May 3, 2026, 7:22 p.m.
Created at: May 3, 2026, 4:06 p.m.