Triple
T34311517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lagoon Amusement Park |
E880458
|
entity |
| Predicate | hasAttraction |
P105
|
FINISHED |
| Object |
Sky Scraper
Sky Scraper is a high-thrill amusement ride located at Lagoon Amusement Park in Utah, known for its intense spinning and towering height.
|
E2090481
|
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: Sky Scraper | Statement: [Lagoon Amusement Park, hasAttraction, Sky Scraper]
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: Sky Scraper Triple: [Lagoon Amusement Park, hasAttraction, Sky Scraper]
Generated description
Sky Scraper is a high-thrill amusement ride located at Lagoon Amusement Park in Utah, known for its intense spinning and towering height.
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_69f349b8bb6c8190ad12a7957a574f04 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71366d1708190ac4f30d12868b130 |
completed | May 3, 2026, 9:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36f9c774a48190a019c4ac137eeae8 |
completed | June 20, 2026, 8:36 p.m. |
| NEDg | Description generation | batch_6a36fa5581dc8190ab4338ac70a8f16a |
completed | June 20, 2026, 8:38 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a36fb292a5c81908ad8344c6ce6c4db |
completed | June 20, 2026, 8:42 p.m. |
Created at: May 1, 2026, 1:57 a.m.