Triple
T2999608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Tories |
E81153
|
entity |
| Predicate | culturalOrientation |
P34206
|
FINISHED |
| Object | traditionalist |
—
|
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: traditionalist | Statement: [High Tories, culturalOrientation, traditionalist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalOrientation Context triple: [High Tories, culturalOrientation, traditionalist]
-
A.
culturalEmphasis
chosen
Indicates that a culture, group, or context places particular importance or priority on a specific value, practice, or domain.
-
B.
positionOnCulture
Indicates the stance, viewpoint, or opinion that one entity holds regarding cultural issues, practices, or phenomena in relation to another entity or context.
-
C.
culturalVariation
Indicates that there are differences in practices, beliefs, or expressions between cultures or within a culture across groups, contexts, or time.
-
D.
culturallySimilarTo
Indicates that two entities share comparable cultural characteristics, practices, or values.
-
E.
culturalExport
Indicates that something originating in one culture is transmitted, adopted, or influential in another culture or region.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f8eb248190b50fd539a06a5a62 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.