Triple
T4280374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Brute |
E97132
|
entity |
| Predicate | usedByAuthorFor |
P42995
|
FINISHED |
| Object | critiquing patriarchal authority |
—
|
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: critiquing patriarchal authority | Statement: [Lady Brute, usedByAuthorFor, critiquing patriarchal authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByAuthorFor Context triple: [Lady Brute, usedByAuthorFor, critiquing patriarchal authority]
-
A.
usedByAuthorTo
chosen
Indicates that something is employed or utilized by an author to achieve a particular purpose or effect.
-
B.
hasAuthor
Indicates that an entity is written or created by a specific author.
-
C.
usedByPerson
Indicates that something (such as an object, tool, or resource) is utilized or employed by a person.
-
D.
basedOnAuthor
Indicates that one entity is derived from, inspired by, or otherwise created on the basis of the work or contributions of a particular author.
-
E.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
- 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_69b34544be3c819084d1ab82d29f90c5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35037b654819087abbb5ea231eefd |
completed | March 12, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69b347fc4c0c8190a7fcd814e27308a5 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.