Triple
T30256665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ribnica River |
E769366
|
entity |
| Predicate | nameWrittenInLatinScript |
P22444
|
FINISHED |
| Object | Ribnica |
—
|
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: Ribnica | Statement: [Ribnica River, nameWrittenInLatinScript, Ribnica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameWrittenInLatinScript Context triple: [Ribnica River, nameWrittenInLatinScript, Ribnica]
-
A.
nameWrittenIn
Indicates that an entity’s name is written or recorded using a specified language, script, or writing system.
-
B.
nameInLatinAlphabet
chosen
Indicates that an entity’s name is written or represented using the Latin alphabet.
-
C.
nameFormInLatin
Indicates that an entity’s name is expressed or recorded in its Latin-language form.
-
D.
titleInLatinScript
Indicates that the title of an entity is written or represented using a Latin-based writing system.
-
E.
nameInLanguageRomanization
Indicates that an entity’s name is represented in the romanized (Latin-script) form of a particular 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f680a511708190a208959af5a8d016 |
completed | May 2, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:41 p.m.