Triple

T38586801
Position Surface form Disambiguated ID Type / Status
Subject Stormwind E932363 entity
Predicate hasDistrict P459 FINISHED
Object Park District
Park District is a scenic, recreational neighborhood within the human capital city of Stormwind in the World of Warcraft universe, known for its greenery and tranquil atmosphere.
E2276811 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: Park District | Statement: [Stormwind, hasDistrict, Park District]
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: Park District
Triple: [Stormwind, hasDistrict, Park District]
Generated description
Park District is a scenic, recreational neighborhood within the human capital city of Stormwind in the World of Warcraft universe, known for its greenery and tranquil atmosphere.

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_69f76ec654d48190b421111cf26e54d9 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcd938241481909d31fa1056a27a21 completed May 7, 2026, 6:26 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41ea9c8ccc819090eadfc322c540d4 completed June 29, 2026, 3:46 a.m.
NEDg Description generation batch_6a41eb6236f88190a95bdb5d26a25e8e completed June 29, 2026, 3:49 a.m.
NED2 Entity disambiguation (via description) batch_6a41ebd65c688190bbc848f604bd9e3c completed June 29, 2026, 3:51 a.m.
Created at: May 3, 2026, 4:32 p.m.