Triple

T13914669
Position Surface form Disambiguated ID Type / Status
Subject 午门 E334588 entity
Predicate 与太和门关系 P57456 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. 皇位継承順位への関係
    Indicates the relationship of an entity to the line of succession to the imperial throne, such as its position, eligibility, or connection within that succession order.
  • B. associatedWithPalace chosen
    Indicates a relationship where an entity has a connection, link, or involvement with a palace, such as through location, function, ownership, or affiliation.
  • C. courtyardRelation
    Indicates a spatial relationship where one entity serves as, is located in, or is directly associated with the courtyard area of another entity.
  • D. associatedWithTempleComplex
    Indicates a relationship in which an entity is connected or related to a specific temple complex, such as by location, function, use, or historical association.
  • E. associatedWithEmperor
    Indicates a relationship in which an entity has a connection, link, or affiliation with an emperor, such as through service, influence, kinship, or shared authority.
  • 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_69d81c5eaa9c819083b1ff8689179565 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de27245c648190b2946845ce0fdbf8 completed April 14, 2026, 11:38 a.m.
PD Predicate disambiguation batch_69de059e4ba881908554f72e889719fa completed April 14, 2026, 9:15 a.m.
Created at: April 9, 2026, 10:16 p.m.