Triple

T28832826
Position Surface form Disambiguated ID Type / Status
Subject Chūō-ku, Fukuoka E728095 entity
Predicate contains P35 FINISHED
Object Tenjin Core shopping complex
Tenjin Core shopping complex is a popular multi-story fashion and lifestyle shopping center located in Fukuoka’s bustling Tenjin district.
E1840049 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: Tenjin Core shopping complex | Statement: [Chūō-ku, Fukuoka, contains, Tenjin Core shopping complex]
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: Tenjin Core shopping complex
Triple: [Chūō-ku, Fukuoka, contains, Tenjin Core shopping complex]
Generated description
Tenjin Core shopping complex is a popular multi-story fashion and lifestyle shopping center located in Fukuoka’s bustling Tenjin district.

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_69f0319dc6088190bbfaa206d40ed74a completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69f6593d67d48190af4c50e85c604a37 completed May 2, 2026, 8:06 p.m.
NED1 Entity disambiguation (via context triple) batch_6a24d3f27738819096a75006a1aceb70 completed June 7, 2026, 2:14 a.m.
NEDg Description generation batch_6a24d9370ef48190845aa485c0356b6f completed June 7, 2026, 2:36 a.m.
NED2 Entity disambiguation (via description) batch_6a24dd72d7288190a98101927bc7eae4 completed June 7, 2026, 2:54 a.m.
Created at: April 28, 2026, 6:38 a.m.