Triple
T21636955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strachan |
E533984
|
entity |
| Predicate | hasModernPronunciationVariant |
P35086
|
FINISHED |
| Object | ˈstrɔːkən |
—
|
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: ˈstrɔːkən | Statement: [Strachan, hasModernPronunciationVariant, ˈstrɔːkən]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernPronunciationVariant Context triple: [Strachan, hasModernPronunciationVariant, ˈstrɔːkən]
-
A.
hasPronunciationDifferenceFrom
Indicates that two linguistic items differ in how they are pronounced.
-
B.
hasVariantSpelling
Indicates that one term is an alternative spelling form of another term.
-
C.
hasVariantReadingsWith
Indicates a relationship where two textual items are linked because they exhibit differing or alternative readings of (typically) the same underlying content.
-
D.
hasAlternativeVocalization
chosen
Indicates that an entity has another valid way it can be vocalized or pronounced, distinct from its primary or standard vocalization.
-
E.
hasStandardPronunciationBasedOn
Indicates that one entity’s standard or canonical pronunciation is determined or derived from another entity’s pronunciation.
- 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_69e0c465ae7481908577b7209fdb2a77 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef538ddb088190a3cba6fdc84c0ae8 |
completed | April 27, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:35 p.m.