Triple
T38639324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amlaive |
E938547
|
entity |
| Predicate | usedInCulturalContext |
P7826
|
FINISHED |
| Object | Gaelic |
—
|
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: Gaelic | Statement: [Amlaive, usedInCulturalContext, Gaelic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInCulturalContext Context triple: [Amlaive, usedInCulturalContext, Gaelic]
-
A.
usedInCulture
chosen
Indicates that something (such as an object, practice, or concept) is employed, referenced, or plays a role within a particular culture or cultural context.
-
B.
originatedInCulturalContext
Indicates that something began, developed, or was created within a particular cultural setting, tradition, or milieu.
-
C.
hasCulturalInterpretation
Indicates that something is understood, represented, or given meaning within a particular cultural context or tradition.
-
D.
usesCulture
Indicates that one entity employs, incorporates, or relies on the cultural practices, norms, or artifacts associated with another entity in its actions or functioning.
-
E.
culturalContextOfWork
Indicates the cultural setting, traditions, or background within which a work was created, interpreted, or is meaningfully situated.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff4de66ba481908e7184b3cf9d4d2d |
completed | May 9, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69ff4c702a5881909c6684c74807e945 |
completed | May 9, 2026, 3:02 p.m. |
Created at: May 3, 2026, 4:32 p.m.