Triple
T25152794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellen Douglas |
E626223
|
entity |
| Predicate | rejectsSuitor |
P69932
|
FINISHED |
| Object | James Fitz-James |
—
|
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: James Fitz-James | Statement: [Ellen Douglas, rejectsSuitor, James Fitz-James]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rejectsSuitor Context triple: [Ellen Douglas, rejectsSuitor, James Fitz-James]
-
A.
refusedMarriageProposalFrom
Indicates that one entity declined or rejected a marriage proposal made by another entity.
-
B.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
C.
rejectedIn
Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
-
D.
rejectedAdvancesOf
chosen
Indicates that one entity declined, refused, or did not accept the romantic or sexual advances made by another entity.
-
E.
rejectedBecause
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f46b84d59881908e038999896aa8f4 |
completed | May 1, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:30 a.m.