Triple
T7608398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Else Garnett |
E180166
|
entity |
| Predicate | portrayedInUniverseAs |
P58964
|
FINISHED |
| Object | working-class housewife |
—
|
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: working-class housewife | Statement: [Else Garnett, portrayedInUniverseAs, working-class housewife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portrayedInUniverseAs Context triple: [Else Garnett, portrayedInUniverseAs, working-class housewife]
-
A.
portraysFictionalUniverse
Indicates that one entity depicts, represents, or presents the fictional universe in which another entity is set.
-
B.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
C.
hasInUniverseRole
chosen
Indicates that an entity holds or performs a specific role or function within a particular fictional or defined universe.
-
D.
portrayedVia
Indicates that one entity is represented, depicted, or expressed through a particular medium, method, or channel.
-
E.
portraysFictionalEntity
Indicates that one entity depicts, represents, or plays the role of a fictional character or figure.
- 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_69c69f3567008190ab01d2ca7b53584a |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6fa1de8a4819091f9e9347835ce16 |
completed | March 27, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:54 p.m.