Triple
T5612749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenock Cemetery |
E147396
|
entity |
| Predicate | placeNameLanguageVariant |
P24399
|
FINISHED |
| Object | Scots |
—
|
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: Scots | Statement: [Greenock Cemetery, placeNameLanguageVariant, Scots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeNameLanguageVariant Context triple: [Greenock Cemetery, placeNameLanguageVariant, Scots]
-
A.
alternateLanguageName
Indicates that an entity has an additional name or label in a different language from its primary or default name.
-
B.
linguisticVariant
Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
-
C.
hasLanguageOfToponym
chosen
Indicates that a place name (toponym) is expressed in or associated with a particular language.
-
D.
hasOfficialNameVariant
Indicates that an entity has an alternative official form or version of its name.
-
E.
languageVariant
Indicates that one language is a variant, dialect, or localized form of another language.
- 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_69c00905d4588190bd967842bbcf2219 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0212143708190b5234407334ab216 |
completed | March 22, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69c01b1b3c98819080687d18ab10a914 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.