Triple
T30769647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surbung |
E783479
|
entity |
| Predicate | hasCulturalTraits |
P3114
|
FINISHED |
| Object | distinct cultural traits |
—
|
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: distinct cultural traits | Statement: [Surbung, hasCulturalTraits, distinct cultural traits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCulturalTraits Context triple: [Surbung, hasCulturalTraits, distinct cultural traits]
-
A.
hasCulturalFeature
chosen
Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
-
B.
hasCulturalConcept
Indicates that an entity embodies, includes, or is associated with a particular cultural idea, value, practice, or construct.
-
C.
hasCulturalRoots
Indicates that something originates from, is shaped by, or is deeply connected to particular cultural traditions, practices, or heritage.
-
D.
hasCulturalExpression
Indicates that an entity embodies, manifests, or is associated with a particular cultural form, practice, or expression.
-
E.
hasCulturalCore
Indicates that one entity embodies or provides the central cultural values, practices, or identity that fundamentally define 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 29, 2026, 8:40 p.m.