Triple
T13911958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Burryman’s Day |
E334518
|
entity |
| Predicate | performedLanguageContext |
P43093
|
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: [The Burryman’s Day, performedLanguageContext, Scots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedLanguageContext Context triple: [The Burryman’s Day, performedLanguageContext, Scots]
-
A.
performedLanguage
chosen
Indicates that an action, work, or performance was carried out using a specified language.
-
B.
performedInContextOf
Indicates that an action or event was carried out within, and is meaningfully related to, a specific situational, procedural, or environmental context.
-
C.
hasLanguageContext
Indicates that an entity is associated with or interpreted within a specific language or linguistic context.
-
D.
nativeLanguageContext
Indicates the relationship in which a language functions as the primary or native linguistic context for an entity’s communication or interpretation.
-
E.
originalLanguageContext
Indicates the language in which something was first created or expressed, providing the original linguistic context for its content or meaning.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2723461881908376b5509ee0d530 |
completed | April 14, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.