Triple
T33700682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Pinchwife |
E863447
|
entity |
| Predicate | triesToControl |
P69335
|
FINISHED |
| Object | Margery Pinchwife |
—
|
NE NERFINISHED |
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: Margery Pinchwife | Statement: [Mr. Pinchwife, triesToControl, Margery Pinchwife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triesToControl Context triple: [Mr. Pinchwife, triesToControl, Margery Pinchwife]
-
A.
triesToTake
Indicates an attempt by one entity to take possession or control of another entity or resource, regardless of whether the attempt succeeds.
-
B.
triesToUse
Indicates an entity’s attempt or effort to make use of another entity, regardless of whether the use is successful.
-
C.
aimsToControl
chosen
Indicates an intention or effort by one entity to gain power over, direct, or regulate another entity or situation.
-
D.
canTry
Indicates that an entity has the possibility or permission to attempt performing a particular action or achieving a certain outcome.
-
E.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fa8ca3808190be2fd9e5fb4c2146 |
completed | May 3, 2026, 7:34 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:43 a.m.