Triple
T19559114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yagüez River |
E489394
|
entity |
| Predicate | hasAlternateNameLanguage |
P63334
|
FINISHED |
| Object | es |
—
|
LITERAL 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: es | Statement: [Yagüez River, hasAlternateNameLanguage, es]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternateNameLanguage Context triple: [Yagüez River, hasAlternateNameLanguage, es]
-
A.
alternateLanguageName
chosen
Indicates that an entity has an additional name or label in a different language from its primary or default name.
-
B.
hasAlternativeFamilyName
Indicates that an entity is associated with an additional or variant family name besides its primary family name.
-
C.
hasAlternateTitleRegion
Indicates that an entity has an alternate title that is specifically used or valid within a particular geographic region.
-
D.
hasLaterNameInEnglish
Indicates that an entity is known by a different English name at a later time or in a subsequent context.
-
E.
haveAlternativeTitle
Indicates that an entity is known by one or more alternative titles or names in addition to its primary title.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63f723d5081909553a4363b579a6b |
completed | April 20, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.