Triple

T34458893
Position Surface form Disambiguated ID Type / Status
Subject Shinkyo Bridge E884578 entity
Predicate nameMeaning P453 FINISHED
Object Sacred Bridge
Sacred Bridge is the English name for Shinkyo Bridge, a historically significant and picturesque vermilion-lacquered bridge at the entrance to the Futarasan Shrine in Nikkō, Japan.
E2096412 NE 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: Sacred Bridge | Statement: [Shinkyo Bridge, nameMeaning, Sacred Bridge]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Sacred Bridge
Triple: [Shinkyo Bridge, nameMeaning, Sacred Bridge]
Generated description
Sacred Bridge is the English name for Shinkyo Bridge, a historically significant and picturesque vermilion-lacquered bridge at the entrance to the Futarasan Shrine in Nikkō, Japan.

Provenance (5 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_69f349c73a94819094dfcf50d00620b8 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7197a35d48190a108b2e55c32dff1 completed May 3, 2026, 9:46 a.m.
NED1 Entity disambiguation (via context triple) batch_6a37184af5d0819086a4a98e466ca82c completed June 20, 2026, 10:46 p.m.
NEDg Description generation batch_6a3718e147708190b72543eb2165bb5e completed June 20, 2026, 10:49 p.m.
NED2 Entity disambiguation (via description) batch_6a37195b2b9c8190a70d9deec095f539 completed June 20, 2026, 10:51 p.m.
Created at: May 1, 2026, 2 a.m.