Triple

T22974029
Position Surface form Disambiguated ID Type / Status
Subject Storks E571263 entity
Predicate setting P1957 FINISHED
Object Stork Mountain
Stork Mountain is a fictional mountainous location commonly depicted as the place where storks originate or gather, often in folklore or animated stories about storks delivering babies.
E2015662 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: Stork Mountain | Statement: [Storks, setting, Stork Mountain]
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: Stork Mountain
Triple: [Storks, setting, Stork Mountain]
Generated description
Stork Mountain is a fictional mountainous location commonly depicted as the place where storks originate or gather, often in folklore or animated stories about storks delivering babies.

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_69e245b2c6548190a0e4c7f2f7df2d48 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f182350b448190a34e5fa0167fd964 completed April 29, 2026, 3:59 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3485e26c948190a519564467e44fe1 completed June 18, 2026, 11:57 p.m.
NEDg Description generation batch_6a3488ed6db88190af9197eb63f35313 completed June 19, 2026, 12:10 a.m.
NED2 Entity disambiguation (via description) batch_6a348a6e63bc8190a6df0a77a51245cc completed June 19, 2026, 12:16 a.m.
Created at: April 17, 2026, 3:48 p.m.