Triple

T38608448
Position Surface form Disambiguated ID Type / Status
Subject Cannonball E934409 entity
Predicate route P5619 FINISHED
Object New York City–Montauk
New York City–Montauk is a popular Long Island travel corridor connecting New York City with the eastern tip of Long Island, known for its beaches and resort towns.
E2280606 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: New York City–Montauk | Statement: [Cannonball, route, New York City–Montauk]
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: New York City–Montauk
Triple: [Cannonball, route, New York City–Montauk]
Generated description
New York City–Montauk is a popular Long Island travel corridor connecting New York City with the eastern tip of Long Island, known for its beaches and resort towns.

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_69f76eccd6d081909ccce171011739a1 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcd96cda148190b19acdd6e7204d90 completed May 7, 2026, 6:26 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41fd52a16c8190a896fdad43b7947f completed June 29, 2026, 5:06 a.m.
NEDg Description generation batch_6a41fed2530c8190b57d2bc1cc2e75c9 completed June 29, 2026, 5:12 a.m.
NED2 Entity disambiguation (via description) batch_6a41ff5fae24819089ccf1dff50e867c completed June 29, 2026, 5:15 a.m.
Created at: May 3, 2026, 4:32 p.m.