Triple
T14053254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leander |
E338145
|
entity |
| Predicate | hasCognate |
P2525
|
FINISHED |
| Object | Leandro |
E904393
|
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: Leandro | Statement: [Leander, hasCognate, Leandro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leandro Context triple: [Leander, hasCognate, Leandro]
-
A.
Leandro
chosen
Leandro is the given first name of Argentine jazz saxophonist and composer Gato Barbieri.
-
B.
Marcelo
Marcelo is a common Portuguese and Spanish given name, notably borne by figures such as Brazilian footballer Marcelo Vieira and former Portuguese Prime Minister Marcelo Caetano.
-
C.
Marcio
Marcio is a masculine given name commonly used in Portuguese- and Spanish-speaking countries, derived from the Latin name Marcius.
-
D.
Reinaldo
Reinaldo is a masculine given name of Spanish and Portuguese origin, equivalent to "Reynaldo" or "Reinald" in English.
-
E.
Aleandro
Aleandro is an Italian surname historically associated with notable Catholic churchmen and papal diplomats.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c8bc54c8190a12f0fc056568538 |
completed | April 14, 2026, 1:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcb65e63b48190bd5bd4a36cd15396 |
completed | May 7, 2026, 3:57 p.m. |
Created at: April 9, 2026, 10:20 p.m.