Triple
T26120812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oja River |
E658959
|
entity |
| Predicate | saidToGiveItsNameTo |
P132742
|
FINISHED |
| Object | La Rioja |
—
|
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: La Rioja | Statement: [Oja River, saidToGiveItsNameTo, La Rioja]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: saidToGiveItsNameTo Context triple: [Oja River, saidToGiveItsNameTo, La Rioja]
-
A.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
-
B.
isNamedFor
Indicates that one entity bears its name in honor of, or derived from, another entity.
-
C.
usedAsNamesakeFor
chosen
Indicates that one entity serves as the source or inspiration for the name given to another entity.
-
D.
nameGivesRiseTo
Indicates that one name, term, or designation leads to, causes, or results in the emergence or establishment of another.
-
E.
commonlyBelievedToBeNamedAfter
Indicates that something is widely thought or popularly assumed to have been named after a particular person, place, or thing, regardless of whether this belief is historically accurate.
- 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60acb357081909b4d9e869e4d2456 |
completed | May 2, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:08 p.m.