Triple

T18370444
Position Surface form Disambiguated ID Type / Status
Subject Goodlettsville, Tennessee E446167 entity
Predicate hasAttraction P105 FINISHED
Object Moss-Wright Park
Moss-Wright Park is a large community park in Goodlettsville, Tennessee, known for its sports fields, walking trails, playgrounds, and recreational facilities.
E1624367 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: Moss-Wright Park | Statement: [Goodlettsville, Tennessee, hasAttraction, Moss-Wright Park]
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: Moss-Wright Park
Triple: [Goodlettsville, Tennessee, hasAttraction, Moss-Wright Park]
Generated description
Moss-Wright Park is a large community park in Goodlettsville, Tennessee, known for its sports fields, walking trails, playgrounds, and recreational facilities.

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_69d8b9f370b88190b1e5081c2c238e7f completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e51751e4288190873bcc4dc140ac16 completed April 19, 2026, 5:56 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0fbcd6237c8190815702e274a30c44 completed May 22, 2026, 2:17 a.m.
NEDg Description generation batch_6a0fbddd0ccc81908036002270cbf4f5 completed May 22, 2026, 2:22 a.m.
NED2 Entity disambiguation (via description) batch_6a0fbf3cf7988190a9d766bfca4ef994 completed May 22, 2026, 2:28 a.m.
Created at: April 10, 2026, 10:44 a.m.