Triple
T37300298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Russell |
E925920
|
entity |
| Predicate | hasSurnameBasis |
P36967
|
FINISHED |
| Object | Russell |
—
|
NE NERFINISHED |
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: Russell | Statement: [Baron Russell, hasSurnameBasis, Russell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurnameBasis Context triple: [Baron Russell, hasSurnameBasis, Russell]
-
A.
hasBaseSurname
chosen
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
-
B.
hasGivenNameBasis
Indicates that one entity’s given name is derived from, based on, or formed using another entity (such as a name, word, or person) as its basis.
-
C.
hasSurnameType
Indicates that an entity’s surname belongs to a particular category or type (e.g., patronymic, toponymic, occupational).
-
D.
hasSurnameBearer
Indicates that a particular surname is borne or carried by a specific person or entity.
-
E.
hasSurnamePrefix
Indicates that one entity’s surname begins with, or is prefixed by, the string or component specified by the other 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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a003ffb548081908ba64fd2b570f42f |
completed | May 10, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_6a003fcecf788190a13dff38b9de3414 |
completed | May 10, 2026, 8:20 a.m. |
Created at: May 3, 2026, 4:16 p.m.