Triple

T9629802
Position Surface form Disambiguated ID Type / Status
Subject Shunpanrō E232567 entity
Predicate hasHistoricalSignboard P43592 FINISHED
Object explanation of Treaty of Shimonoseki 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: explanation of Treaty of Shimonoseki | Statement: [Shunpanrō, hasHistoricalSignboard, explanation of Treaty of Shimonoseki]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricalSignboard
Context triple: [Shunpanrō, hasHistoricalSignboard, explanation of Treaty of Shimonoseki]
  • A. hasHistoricMarker chosen
    Indicates that something is associated with or identified by an official historic marker or plaque recognizing its historical significance.
  • B. hasHistoricalSignificance
    Indicates that something possesses notable importance or influence within a historical context or period.
  • C. hasHistoricalSection
    Indicates that something includes a dedicated part or segment that presents historical information or context.
  • D. hasHistoricalEntity
    Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical context.
  • E. hasHistoricSite
    Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
  • 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_69ca848793ec8190a93a12383a754dc0 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9b01863c8190a9ec4684804f96bc completed April 1, 2026, 10:24 p.m.
PD Predicate disambiguation batch_69ccd5acfa5c8190aaba3cf548723604 completed April 1, 2026, 8:22 a.m.
Created at: March 30, 2026, 8:10 p.m.