Triple
T11007567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crimean Tatar toponyms |
E260160
|
entity |
| Predicate | containSemanticFields |
P91671
|
FINISHED |
| Object | geographical features |
—
|
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: geographical features | Statement: [Crimean Tatar toponyms, containSemanticFields, geographical features]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containSemanticFields Context triple: [Crimean Tatar toponyms, containSemanticFields, geographical features]
-
A.
hasSemantics
Indicates that one entity carries or encodes the meaning, interpretation, or semantic content associated with another entity.
-
B.
hasSemanticRestriction
Indicates that a concept or relation is constrained in meaning or usage by specific semantic conditions or limitations.
-
C.
hasSemanticsDefinedBy
Indicates that the meaning or interpretation of one entity is specified, constrained, or determined by another entity.
-
D.
семантическоеПоле
chosen
Indicates that entities are related by belonging to the same semantic field, i.e., they share a common area of meaning or conceptual domain.
-
E.
containsAsSubfield
Indicates that one field or data structure includes another field as a nested or component subfield within it.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79757bdcc8190900b267826eece21 |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.