Triple
T14203749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heini |
E352029
|
entity |
| Predicate | culturalRegister |
P113195
|
FINISHED |
| Object | informal |
—
|
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: informal | Statement: [Heini, culturalRegister, informal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalRegister Context triple: [Heini, culturalRegister, informal]
-
A.
culturalElements
Indicates a relationship where certain elements (such as practices, symbols, or artifacts) belong to, express, or characterize a particular culture or cultural context.
-
B.
culturalCategory
Indicates that one entity classifies or groups another entity according to a particular culture, tradition, or culturally defined type.
-
C.
culturalType
Indicates the classification of something according to its cultural category, style, or tradition.
-
D.
culturalKnowledge
Indicates that one entity possesses or conveys understanding of the customs, practices, values, or traditions associated with a particular culture.
-
E.
hasCulturalSignificanceFor
Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
- F. None of above. chosen
Provenance (4 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61f6d4d481909128084e82e6a58a |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:05 a.m.