Triple
T11533989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riccardo |
E273497
|
entity |
| Predicate | cognate |
P2527
|
FINISHED |
| Object | Richard (English) |
E19643
|
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: Richard (English) | Statement: [Riccardo, cognate, Richard (English)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Richard (English) Context triple: [Riccardo, cognate, Richard (English)]
-
A.
Rex Anglorum
Rex Anglorum is a Latin royal title historically used to denote the "King of the English" in medieval England.
-
B.
Richard
chosen
Richard is a common masculine given name of Germanic origin, widely used in English-speaking countries.
-
C.
Edward
Edward is a masculine given name of English origin, historically associated with kings of England and notable figures such as U.S. Senator Edward M. Kennedy.
-
D.
Stuart
Stuart is a small coastal city in Florida known for its historic downtown, boating and fishing, and location along the Treasure Coast.
-
E.
Stuart
Stuart is a masculine given name of Scottish origin, traditionally derived from the occupational surname "Stewart" meaning a household guardian or steward.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8839a2c7081909c285d1f6beb971c |
completed | April 10, 2026, 4:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e68577f5ec8190a46687119d288a36 |
completed | April 20, 2026, 7:58 p.m. |
Created at: April 8, 2026, 9:37 p.m.