Triple
T17800801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Litava River |
E444418
|
entity |
| Predicate | hasNameLanguageCode |
P13919
|
FINISHED |
| Object | cs |
—
|
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: cs | Statement: [Litava River, hasNameLanguageCode, cs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameLanguageCode Context triple: [Litava River, hasNameLanguageCode, cs]
-
A.
hasNameInLocalLanguage
Indicates that an entity is associated with a name expressed in the local or native language of a given context or region.
-
B.
hasLinguisticCode
chosen
Indicates that an entity is associated with a specific linguistic identifier or code (such as a language or script code) that characterizes its linguistic properties.
-
C.
hasCodenameLanguage
Indicates that a codename is expressed or defined in a particular language.
-
D.
isNamedLanguage
Indicates that a language entity bears a specific name or designation.
-
E.
hasLocaleName
Indicates that an entity has a specific name or label used in a particular language or regional locale.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e487ff42108190b82ceb4466aa2dff |
completed | April 19, 2026, 7:45 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:13 a.m.