Triple
T13564352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Murchison |
E323993
|
entity |
| Predicate | expectsFromBeneatha |
P32577
|
FINISHED |
| Object | traditional femininity |
—
|
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: traditional femininity | Statement: [George Murchison, expectsFromBeneatha, traditional femininity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectsFromBeneatha Context triple: [George Murchison, expectsFromBeneatha, traditional femininity]
-
A.
requiresBeliefIn
Indicates that one entity can only be valid, accessible, or fulfilled if belief in another specified entity or proposition is held.
-
B.
exhortedBy
Indicates that one entity is strongly urged, encouraged, or admonished to act or think in a certain way by another entity.
-
C.
exhortedTo
Indicates that one entity strongly urged, encouraged, or pressured another entity to perform a particular action or adopt a certain course of behavior.
-
D.
endedFor
Indicates that a particular event, state, or process has come to an end for a specified entity or participant.
-
E.
isSupposedToBe
chosen
Indicates that something is expected or intended to have a particular state, quality, or role, whether or not it actually does.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00bbe848190bb33efe2af528295 |
completed | April 12, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:47 p.m.