Triple
T25043302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morris |
E627168
|
entity |
| Predicate | birthName |
P65
|
FINISHED |
| Object |
Maurice De Bevere
Maurice De Bevere, better known by his pen name Morris, was a Belgian cartoonist famed for creating the classic Western comic series "Lucky Luke."
|
E1681780
|
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: Maurice De Bevere | Statement: [Morris, birthName, Maurice De Bevere]
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: Maurice De Bevere Triple: [Morris, birthName, Maurice De Bevere]
Generated description
Maurice De Bevere, better known by his pen name Morris, was a Belgian cartoonist famed for creating the classic Western comic series "Lucky Luke."
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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4530d80148190b959bb48ff7e0c2f |
completed | May 1, 2026, 7:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10ad34f73081909da237769fc77747 |
completed | May 22, 2026, 7:23 p.m. |
| NEDg | Description generation | batch_6a10add7365481908143c97cbd5a75e8 |
completed | May 22, 2026, 7:26 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a10ae653e788190b52f77bdc2faa970 |
completed | May 22, 2026, 7:28 p.m. |
Created at: April 18, 2026, 6:08 a.m.