Triple
T10058660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Lewis Macie |
E208925
|
entity |
| Predicate | legalNameChangeDate |
P801
|
FINISHED |
| Object | 1800-00-00 |
—
|
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: 1800-00-00 | Statement: [James Lewis Macie, legalNameChangeDate, 1800-00-00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalNameChangeDate Context triple: [James Lewis Macie, legalNameChangeDate, 1800-00-00]
-
A.
nameChangeDate
chosen
Indicates the date on which an entity’s name was officially changed.
-
B.
officialNameChangeTo
Indicates that an entity’s official name has been changed from a previous name to a new specified name.
-
C.
underwentNameChangeTo
Indicates that an entity previously known by one name has changed its name to the specified new name.
-
D.
changedSurnameFrom
Indicates that an entity has adopted a new surname that was previously a different, specified surname.
-
E.
hasSubsequentNameChange
Indicates that an entity undergoes a later change to its name, resulting in a new official designation after the original.
- 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcfb0f17c8190a8c0cfb02863537d |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:57 p.m.