Triple

T34182240
Position Surface form Disambiguated ID Type / Status
Subject Robert F. Swinnie Airport E876851 entity
Predicate namedAfter P63 FINISHED
Object Robert F. Swinnie
Robert F. Swinnie was a local figure of sufficient prominence—likely in aviation, public service, or community leadership—to have an airport named in his honor.
E2218548 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: Robert F. Swinnie | Statement: [Robert F. Swinnie Airport, namedAfter, Robert F. Swinnie]
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: Robert F. Swinnie
Triple: [Robert F. Swinnie Airport, namedAfter, Robert F. Swinnie]
Generated description
Robert F. Swinnie was a local figure of sufficient prominence—likely in aviation, public service, or community leadership—to have an airport named in his honor.

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_69f349ae640c8190b9cd220b5368d8b6 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7100635d481909a201b11a27f181b completed May 3, 2026, 9:06 a.m.
NED1 Entity disambiguation (via context triple) batch_6a40439950848190aae285ab7d680023 completed June 27, 2026, 9:41 p.m.
NEDg Description generation batch_6a40448854a88190852646c14a8f9864 completed June 27, 2026, 9:45 p.m.
NED2 Entity disambiguation (via description) batch_6a404505b4048190bfadd456a3214fe1 completed June 27, 2026, 9:47 p.m.
Created at: May 1, 2026, 1:55 a.m.