Triple
T9644713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Карымский |
E233164
|
entity |
| Predicate | составЛав |
P14960
|
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.
compositionForm
Indicates the structural or organizational form in which something is composed or arranged.
-
B.
lays
Indicates that one entity deposits or places something, typically eggs or objects, onto a surface or in a location.
-
C.
constitutedBy
chosen
Indicates that something is made up of, composed from, or formed by the specified parts or elements.
-
D.
compositionChamber
Indicates a relationship where a chamber or enclosed space is used as the setting or environment in which a composition (such as a musical, chemical, or artistic work) is created or formed.
-
E.
forcesComposition
Indicates that one entity compels or determines the structural makeup or arrangement of another entity.
- 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.