Triple
T21126740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kernewek Kemmyn |
E520576
|
entity |
| Predicate | aimsToReflect |
P3935
|
FINISHED |
| Object | Cornish phonology |
—
|
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: Cornish phonology | Statement: [Kernewek Kemmyn, aimsToReflect, Cornish phonology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimsToReflect Context triple: [Kernewek Kemmyn, aimsToReflect, Cornish phonology]
-
A.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
B.
reflects
chosen
Indicates that one entity (often a surface, medium, or representation) throws back, mirrors, or otherwise shows an image, property, or state of another entity.
-
C.
aimsToBalance
Indicates an intention or effort by one entity to bring multiple elements, forces, or conditions into a state of equilibrium.
-
D.
aimsToServeAs
Indicates that one entity has the intention or purpose of functioning in the role or capacity of another entity.
-
E.
aimsToModel
Indicates that one entity is intended or designed to represent, simulate, or approximate the behavior, structure, or properties 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72239965c819081b4077b914d0a98 |
completed | April 21, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.