Triple
T28776746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Crawford |
E726552
|
entity |
| Predicate | proposalOutcomeWithFannyPrice |
P58224
|
FINISHED |
| Object | rejected |
—
|
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: rejected | Statement: [Henry Crawford, proposalOutcomeWithFannyPrice, rejected]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposalOutcomeWithFannyPrice Context triple: [Henry Crawford, proposalOutcomeWithFannyPrice, rejected]
-
A.
proposalOutcome
chosen
Indicates the result or status assigned to a proposal after it has been evaluated or decided upon.
-
B.
offersOutcome
Indicates that one entity provides or makes available a particular result, consequence, or benefit to another entity.
-
C.
proposalSolicitedBy
Indicates that a proposal was requested or invited by a particular party or entity.
-
D.
bidOutcome
Indicates the result or status of a bidding process or offer made in a competitive context.
-
E.
proposalType
Indicates the specific category or kind of proposal associated with an entity or event.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 28, 2026, 6:18 a.m.