Triple
T13221736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gens Sulpicia |
E314770
|
entity |
| Predicate | hasCognomen |
P6662
|
FINISHED |
| Object | Rufus |
E721282
|
NE 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: Rufus | Statement: [gens Sulpicia, hasCognomen, Rufus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rufus Context triple: [gens Sulpicia, hasCognomen, Rufus]
-
A.
Rufus
Rufus was a 1970s American funk and R&B band best known for launching Chaka Khan’s career and for hits like “Tell Me Something Good” and “Ain’t Nobody.”
-
B.
Rufus
chosen
Rufus is a cognomen historically used by members of the Roman gens Octavia, distinguishing a particular family branch within that lineage.
-
C.
Rufus
Rufus is a French actor best known internationally for his supporting role in the whimsical film "Amélie."
-
D.
Rufus
Rufus is a masculine given name of Latin origin meaning "red-haired" or "red."
-
E.
Rufus
Rufus is a figure mentioned in the New Testament, traditionally identified as a Christian in Rome greeted by the Apostle Paul and believed to be the son of Simon of Cyrene.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf74d708190a61d8ad938653b06 |
completed | April 10, 2026, 11:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f76b9a5e388190ab75b9f476216894 |
completed | May 3, 2026, 3:36 p.m. |
Created at: April 9, 2026, 9:18 p.m.