Triple
T33478164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Collins’s proposal to Elizabeth Bennet |
E857382
|
entity |
| Predicate | ElizabethResponse |
P173047
|
FINISHED |
| Object | rejection |
—
|
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: rejection | Statement: [Mr. Collins’s proposal to Elizabeth Bennet, ElizabethResponse, rejection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ElizabethResponse Context triple: [Mr. Collins’s proposal to Elizabeth Bennet, ElizabethResponse, rejection]
-
A.
JesusResponsePattern
Indicates the characteristic way Jesus typically responds in a given situation, including his manner, tone, or type of action taken.
-
B.
answeredBy
Indicates that a question, request, or problem is responded to or resolved by a particular entity.
-
C.
responseStatement
chosen
Indicates that an entity provides a reply or answer, typically in response to a prior statement, question, or situation.
-
D.
replyFormat
Indicates the specific structure or style in which a reply or response should be presented.
-
E.
typicalResponse
Indicates that an entity’s behavior, reaction, or outcome is the standard or commonly expected response in a given context or situation.
- 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e52c1a848190b35743f9e5361969 |
completed | May 3, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:38 a.m.