Triple
T8405912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacques-Louis Macie |
E198496
|
entity |
| Predicate | hasNameChange |
P60916
|
FINISHED |
| Object | changed surname from Macie to Smithson |
—
|
LITERAL 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: changed surname from Macie to Smithson | Statement: [Jacques-Louis Macie, hasNameChange, changed surname from Macie to Smithson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameChange Context triple: [Jacques-Louis Macie, hasNameChange, changed surname from Macie to Smithson]
-
A.
hasSubsequentNameChange
Indicates that an entity undergoes a later change to its name, resulting in a new official designation after the original.
-
B.
changedNameOn
Indicates that an entity altered or updated its name at a specific point in time or on a particular date.
-
C.
changedNameIn
Indicates that an entity has altered or adopted a different name within a specific context, time period, or jurisdiction.
-
D.
underwentNameChangeTo
chosen
Indicates that an entity previously known by one name has changed its name to the specified new name.
-
E.
hasNameBeforeChange
Indicates that an entity is associated with the name it had prior to some change or renaming event.
- F. None of above.
Provenance (3 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_69ca8310df9c8190b25f16161cca3e41 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb8312941c8190af0b2def0a4e02be |
completed | March 31, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:05 p.m.