Triple
T6930050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman |
E160408
|
entity |
| Predicate | hasCognate |
P2525
|
FINISHED |
| Object | Romano |
E632793
|
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: Romano | Statement: [Roman, hasCognate, Romano]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Romano Context triple: [Roman, hasCognate, Romano]
-
A.
Romano
Romano Mussolini was an Italian jazz pianist and painter, known both for his musical career and for being the son of dictator Benito Mussolini.
-
B.
Román
Román is a given name and surname of Latin origin, commonly used in Spanish-speaking countries.
-
C.
Römer
The Römer is Frankfurt am Main’s historic city hall complex, renowned for its distinctive stepped gabled façade and long-standing role as a center of municipal government.
-
D.
Rromani
Rromani refers to the Roma people, an ethnic group of traditionally itinerant communities with origins in the Indian subcontinent and a widespread presence across Europe and beyond.
-
E.
Romão
chosen
Romão is a Portuguese given name and surname derived from the Latin name Romanus, commonly associated with Roman heritage.
- 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_69c6884e15208190b9e91487eaafcf85 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6da1f5fcc8190b43f53f90fc1821c |
completed | March 27, 2026, 7:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c769fa17748190a1ca72ca86cce827 |
completed | March 28, 2026, 5:41 a.m. |
Created at: March 27, 2026, 2:27 p.m.