Triple

T28798834
Position Surface form Disambiguated ID Type / Status
Subject John J. Burns Park E727169 entity
Predicate namedAfter P63 FINISHED
Object John J. Burns
John J. Burns was a public figure commemorated by the naming of John J. Burns Park, likely recognized for his civic or community contributions.
 E1912305 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: John J. Burns | Statement: [John J. Burns Park, namedAfter, John J. Burns]
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: John J. Burns
Triple: [John J. Burns Park, namedAfter, John J. Burns]
Generated description
John J. Burns was a public figure commemorated by the naming of John J. Burns Park, likely recognized for his civic or community contributions.

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_69f0319b7c44819085736bcc256185e6 completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69f658a91ba0819084fbe3dd8a09f7cd completed May 2, 2026, 8:03 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2789180a8081909ece1a5efc079764 completed June 9, 2026, 3:31 a.m.
NEDg Description generation batch_6a278a1d4c0881909d4e6ae051872ba5 completed June 9, 2026, 3:35 a.m.
NED2 Entity disambiguation (via description) batch_6a278b7daf3c819090c29e305656692d completed June 9, 2026, 3:41 a.m.
Created at: April 28, 2026, 6:26 a.m.