Triple
T34625612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maycomb County, Alabama |
E889126
|
entity |
| Predicate | depictsSocialStructure |
P8216
|
FINISHED |
| Object | rigid racial hierarchy |
—
|
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: rigid racial hierarchy | Statement: [Maycomb County, Alabama, depictsSocialStructure, rigid racial hierarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsSocialStructure Context triple: [Maycomb County, Alabama, depictsSocialStructure, rigid racial hierarchy]
-
A.
depictsSocietyType
Indicates that one entity visually represents or portrays the type or structure of a particular society associated with another entity.
-
B.
hasSocialStructure
chosen
Indicates that an entity exhibits an organized pattern of social relationships or hierarchy among its members.
-
C.
portraysSocialTypes
Indicates that an entity depicts or represents particular social roles, groups, or character types.
-
D.
depicts
Indicates that one entity visually represents, portrays, or shows another entity.
-
E.
speciesStructure
Indicates the structural or organizational characteristics that define how a species is composed or arranged.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 1, 2026, 2:04 a.m.