Triple
T12884602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Tulliver |
E308192
|
entity |
| Predicate | declaresIntentionTo |
P88492
|
FINISHED |
| Object | pay off all his debts |
—
|
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: pay off all his debts | Statement: [Mr. Tulliver, declaresIntentionTo, pay off all his debts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declaresIntentionTo Context triple: [Mr. Tulliver, declaresIntentionTo, pay off all his debts]
-
A.
intendsTo
chosen
Indicates that one entity has the purpose, plan, or desire to perform an action involving another entity or outcome.
-
B.
intendedWith
Indicates that one entity is the planned or desired target, recipient, or context for the use or application of another entity.
-
C.
typicalIntentionsInclude
Indicates that one entity’s usual or characteristic intentions encompass or include the other entity or action.
-
D.
intendedToCreate
Indicates that one entity performed an action or was designed with the purpose or goal of bringing another entity into existence or causing it to come about.
-
E.
patronIntention
Indicates that a patron has a specific intended action, purpose, or goal directed toward 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97c7f91d08190aac2f6419d3ba992 |
completed | April 10, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69d96fa55b888190ab1612e93c41aec4 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:39 p.m.