Triple
T9644714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Карымский |
E233164
|
entity |
| Predicate | форма |
P1464
|
FINISHED |
| Object | правильный конический вулканический конус |
—
|
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: правильный конический вулканический конус | Statement: [Карымский, форма, правильный конический вулканический конус]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: форма Context triple: [Карымский, форма, правильный конический вулканический конус]
-
A.
shape
chosen
Indicates that one entity has a particular geometric or physical form characterized by the other entity.
-
B.
الشكل
Indicates a relationship where one entity represents, takes, or describes the form, shape, or configuration of another entity.
-
C.
shaped
Indicates that one entity has given form, contour, or structure to another entity or outcome.
-
D.
governingForm
Indicates that one entity specifies or embodies the authoritative rules, structure, or format that control or regulate another entity.
-
E.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
- 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_69ca848a5a908190aad251f4137b0c3a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b7fd2308190803a196ecdc80d76 |
completed | April 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:12 p.m.