Triple
T28155982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christy Beam |
E714747
|
entity |
| Predicate | hasChild |
P369
|
FINISHED |
| Object |
Adelynn Beam
Adelynn Beam is the daughter of author Christy Beam, whose family’s experiences with faith and healing inspired the book and film "Miracles from Heaven."
|
E1807464
|
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: Adelynn Beam | Statement: [Christy Beam, hasChild, Adelynn Beam]
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: Adelynn Beam Triple: [Christy Beam, hasChild, Adelynn Beam]
Generated description
Adelynn Beam is the daughter of author Christy Beam, whose family’s experiences with faith and healing inspired the book and film "Miracles from Heaven."
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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f641e667f88190928bd3315a0dc485 |
completed | May 2, 2026, 6:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a15e6a57b0c8190a598e61622e1ada2 |
completed | May 26, 2026, 6:29 p.m. |
| NEDg | Description generation | batch_6a15e8594e948190b8b17f9ba8444702 |
completed | May 26, 2026, 6:37 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a15e8eb865c819082e07edcaca201c7 |
completed | May 26, 2026, 6:39 p.m. |
Created at: April 27, 2026, 10:02 p.m.