Triple
T473781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Svans |
E9015
|
entity |
| Predicate | cultureType |
P3114
|
FINISHED |
| Object | highland culture |
—
|
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: highland culture | Statement: [Svans, cultureType, highland culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultureType Context triple: [Svans, cultureType, highland culture]
-
A.
culturalMovement
Indicates that an entity is associated with, participates in, or belongs to a particular cultural movement or trend.
-
B.
culturalTradition
Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
-
C.
culturalExport
Indicates that something originating in one culture is transmitted, adopted, or influential in another culture or region.
-
D.
hasCulturalFeature
chosen
Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
-
E.
culturalOrganization
Indicates that an entity is an organization whose primary purpose involves cultural activities, preservation, or promotion.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0208c788190a96cdabcf593fda7 |
completed | Feb. 28, 2026, 1:39 p.m. |
| PD | Predicate disambiguation | batch_69a2edeed31881908cf43beed410572d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.