Triple
T4501595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivor Novello |
E101230
|
entity |
| Predicate | usedSurnameFrom |
P23349
|
FINISHED |
| Object | his mother’s middle name "Novello" |
—
|
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: his mother’s middle name "Novello" | Statement: [Ivor Novello, usedSurnameFrom, his mother’s middle name "Novello"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedSurnameFrom Context triple: [Ivor Novello, usedSurnameFrom, his mother’s middle name "Novello"]
-
A.
usedAsSurname
chosen
Indicates that something functions as a family name borne by a person or group of people.
-
B.
usedWithSurname
Indicates that something (typically a given name or title) is used together with a particular surname in naming or reference.
-
C.
changedSurnameFrom
Indicates that an entity has adopted a new surname that was previously a different, specified surname.
-
D.
associatedSurname
Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
-
E.
changedSurnameTo
Indicates that an entity has adopted a new surname, replacing their previous one, with the new surname specified as the related entity.
- 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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56f9dca08190b926f40e201a3e97 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1 p.m.