Triple
T25572393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ural-batyr |
E641008
|
entity |
| Predicate | influencesToponymy |
P98810
|
FINISHED |
| Object | Ural Mountains |
—
|
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: Ural Mountains | Statement: [Ural-batyr, influencesToponymy, Ural Mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influencesToponymy Context triple: [Ural-batyr, influencesToponymy, Ural Mountains]
-
A.
influenceOnToponymy
chosen
Indicates that one entity has affected or shaped the naming, form, or development of place names associated with another entity.
-
B.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of another entity.
-
C.
hasToponymicMotivation
Indicates that something is motivated, derived, or named based on a place name (toponym).
-
D.
hasEthnolinguisticOriginOfToponym
Indicates that a toponym (place name) originates from or is derived from a particular ethnolinguistic group or language.
-
E.
toponymsShareSpelling
Indicates that two place names share the same or very similar written form or spelling.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 21, 2026, 3:59 p.m.