Triple
T28575347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burger King |
E723224
|
entity |
| Predicate | founder |
P104
|
FINISHED |
| Object |
James McLamore
James McLamore was an American entrepreneur best known for co-founding and expanding the Burger King fast-food restaurant chain.
|
E1826114
|
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: James McLamore | Statement: [Burger King, founder, James McLamore]
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: James McLamore Triple: [Burger King, founder, James McLamore]
Generated description
James McLamore was an American entrepreneur best known for co-founding and expanding the Burger King fast-food restaurant chain.
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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f650c7d5ac81908b1764972e438168 |
completed | May 2, 2026, 7:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1cb6eff2e88190ae822e9c03377779 |
completed | May 31, 2026, 10:32 p.m. |
| NEDg | Description generation | batch_6a1cba824efc819080e74d94c5cc364e |
completed | May 31, 2026, 10:47 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a1cbb2239708190ae49cb11c399e99f |
completed | May 31, 2026, 10:50 p.m. |
Created at: April 28, 2026, 4:12 a.m.