Triple
T37867632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Río Darro |
E944517
|
entity |
| Predicate | tambiénLlamadoHistóricamente |
P145623
|
FINISHED |
| Object | río de la Plata |
—
|
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: río de la Plata | Statement: [Río Darro, tambiénLlamadoHistóricamente, río de la Plata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tambiénLlamadoHistóricamente Context triple: [Río Darro, tambiénLlamadoHistóricamente, río de la Plata]
-
A.
historicalNameUsedIn
chosen
Indicates that a historical or former name was used to refer to a particular entity in some context.
-
B.
historicallyRecognizedAs
Indicates that an entity has been acknowledged or designated under a particular name, status, or role during a past historical period.
-
C.
historicallyBorneBy
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
-
D.
historicallyLinked
Indicates that two entities are connected through a shared or related historical event, period, or development.
-
E.
historicalNameInSpanish
Indicates that an entity is known or referred to by a particular historical name when expressed in the Spanish language.
- 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.