Triple
T18338611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mother |
E439338
|
entity |
| Predicate | lyricalAddressTo |
P82504
|
FINISHED |
| Object | John Lennon's mother |
—
|
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: John Lennon's mother | Statement: [Mother, lyricalAddressTo, John Lennon's mother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricalAddressTo Context triple: [Mother, lyricalAddressTo, John Lennon's mother]
-
A.
addressing
chosen
Indicates that one entity is directing speech, communication, or attention specifically toward another entity.
-
B.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
-
C.
locationAddressed
Indicates that a communication, message, or action is specifically directed to or intended for a particular location or address.
-
D.
addressedBy
Indicates that something (such as an issue, request, or item) is handled, dealt with, or responded to by a particular agent or entity.
-
E.
enactedToAddress
Indicates that something (such as a law, policy, or measure) was formally put into effect specifically to deal with or remedy a particular issue, problem, or need.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50ecf3b4c81909372630ab634dd43 |
completed | April 19, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:37 a.m.