Triple
T24872689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darry Curtis |
E622476
|
entity |
| Predicate | reasonForLostOpportunity |
P157426
|
FINISHED |
| Object | responsibility for his brothers |
—
|
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: responsibility for his brothers | Statement: [Darry Curtis, reasonForLostOpportunity, responsibility for his brothers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForLostOpportunity Context triple: [Darry Curtis, reasonForLostOpportunity, responsibility for his brothers]
-
A.
lostOpportunity
chosen
Indicates that a potential benefit, advantage, or desired outcome that could have been achieved through an action or relationship was missed or not realized.
-
B.
lostStatusReason
Indicates the reason or cause for which something transitioned into a lost or unsuccessful status.
-
C.
reasonForLossOfVote
Indicates the specific cause or circumstance that led to an entity losing its right or ability to vote.
-
D.
reasonForContactLoss
Indicates the cause or circumstance that led to the loss or termination of contact between entities.
-
E.
reasonForReoffer
Indicates the reason or justification for presenting something again after it was previously offered.
- 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 5:23 a.m.