Triple
T19251431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joanna |
E481401
|
entity |
| Predicate | supportMethod |
P47879
|
FINISHED |
| Object | providing for them out of her means |
—
|
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: providing for them out of her means | Statement: [Joanna, supportMethod, providing for them out of her means]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportMethod Context triple: [Joanna, supportMethod, providing for them out of her means]
-
A.
supportFunction
Indicates that one entity provides assistance, resources, or functionality that enables or enhances the operation or effectiveness of another entity.
-
B.
supportBase
Indicates that one entity serves as a foundational or backing structure that physically or functionally supports another entity.
-
C.
supportStyle
chosen
Indicates the manner or approach by which one entity provides assistance or backing to another.
-
D.
support
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
-
E.
supportPolicy
Indicates that one entity endorses, backs, or helps to maintain a particular policy or course of action.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb30bf6c819094c44aceb544a023 |
completed | April 20, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:27 p.m.