Triple
T8416215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Party |
E198735
|
entity |
| Predicate | hasClassBelow |
P36307
|
FINISHED |
| Object | the proles |
—
|
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: the proles | Statement: [The Party, hasClassBelow, the proles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClassBelow Context triple: [The Party, hasClassBelow, the proles]
-
A.
hasClass
Indicates that an entity belongs to, is categorized under, or is associated with a particular class or type.
-
B.
hasClassGroup
Indicates that an entity belongs to or is associated with a particular class group or category.
-
C.
occursBelow
Indicates that one event or object takes place or is positioned at a lower level or beneath another in a spatial or hierarchical sense.
-
D.
classBelow
chosen
Indicates that one class is positioned lower than another in a hierarchy, ordering, or structural arrangement.
-
E.
hasAncestor
Indicates that one entity is an ancestor (direct or indirect, such as a parent, grandparent, etc.) of another entity in a genealogical or hierarchical lineage.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb84c5121081908efa3eca25406d3a |
completed | March 31, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.