Triple
T25070236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langholm, North Carolina |
E627887
|
entity |
| Predicate | hasCulturalLinkTo |
P153856
|
FINISHED |
| Object | Scotland |
—
|
NE NERFINISHED |
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: Scotland | Statement: [Langholm, North Carolina, hasCulturalLinkTo, Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCulturalLinkTo Context triple: [Langholm, North Carolina, hasCulturalLinkTo, Scotland]
-
A.
hasCulturalRelation
Indicates a relationship in which entities are connected through shared, influencing, or interacting cultural practices, values, traditions, or expressions.
-
B.
hasCulturalHeritageLink
chosen
Indicates a relationship where one entity is culturally derived from, influenced by, or historically connected to another.
-
C.
hasAssociatedCulture
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
-
D.
hasCulturalEquivalent
Indicates that one entity has a counterpart in another cultural context that plays a similar role, function, or meaning.
-
E.
hasCulturalDimensionWith
Indicates that one entity possesses or is associated with a particular cultural dimension in relation to another entity.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 18, 2026, 6:10 a.m.