Triple
T35127195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rufus (surname) |
E1014339
|
entity |
| Predicate | isRelatedGivenName |
P3889
|
FINISHED |
| Object | Rufus |
—
|
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: Rufus | Statement: [Rufus (surname), isRelatedGivenName, Rufus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRelatedGivenName Context triple: [Rufus (surname), isRelatedGivenName, Rufus]
-
A.
isRelatedName
chosen
Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
-
B.
isCourtesyNameOf
Indicates that one name is the courtesy name (formal adult name) traditionally used to refer to a specific person.
-
C.
isRelatedSymbol
Indicates that one symbol has a defined relationship or association with another symbol, such as similarity, correspondence, or functional connection.
-
D.
isGivenName
Indicates that one entity is the personal (given) name of another entity.
-
E.
isPaternalFamilyNameOf
Indicates that one name is the paternal (father’s-side) family surname borne by a given person.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.