Triple
T7647844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | society of Virginia |
E173169
|
entity |
| Predicate | hasCulturalIssue |
P53143
|
FINISHED |
| Object | slavery |
—
|
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: slavery | Statement: [society of Virginia, hasCulturalIssue, slavery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCulturalIssue Context triple: [society of Virginia, hasCulturalIssue, slavery]
-
A.
culturalIssue
chosen
Indicates that something pertains to, arises from, or significantly affects the beliefs, values, practices, or norms of a particular culture or group.
-
B.
hasCulturalShift
Indicates a change in the prevailing beliefs, values, norms, or practices within a group, organization, or society over time.
-
C.
hasCulturalReception
Indicates that an entity has been received, interpreted, or responded to within a particular cultural context or by a specific audience.
-
D.
hasCulturalInterpretation
Indicates that something is understood, represented, or given meaning within a particular cultural context or tradition.
-
E.
hasCulturalPerspective
Indicates a relationship where something is understood, interpreted, or presented from a particular cultural viewpoint or frame of reference.
- 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_69c6995360188190968ee57b72a1627f |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faf6328c8190bce0a3f8a17ef890 |
completed | March 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e9ef1c81909c8bff716541ac1f |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:58 p.m.