Triple
T2459126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Vowel Length Rule |
E54489
|
entity |
| Predicate | isRealizedAs |
P39259
|
FINISHED |
| Object | predictable vowel length differences |
—
|
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: predictable vowel length differences | Statement: [Scottish Vowel Length Rule, isRealizedAs, predictable vowel length differences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRealizedAs Context triple: [Scottish Vowel Length Rule, isRealizedAs, predictable vowel length differences]
-
A.
hasRealizationAs
chosen
Indicates that something abstract, such as a plan, design, or concept, is concretely implemented or manifested as a particular realized form.
-
B.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
C.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
D.
constructedAs
Indicates that one entity is built, formed, or created in the manner, structure, or configuration specified by another entity.
-
E.
envisionedAs
Indicates that one entity is mentally pictured, imagined, or conceived in terms of another entity or role.
- 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_69ab49dee84c819096b50a0049c347ac |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd49c5aa081909ab4f726a458b77f |
completed | March 7, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69abd0b199488190aa381b36593ae1ac |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:44 p.m.