Triple
T27617563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belle Reeve |
E700479
|
entity |
| Predicate | lossReason |
P155966
|
FINISHED |
| Object | debts and mortgages |
—
|
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: debts and mortgages | Statement: [Belle Reeve, lossReason, debts and mortgages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lossReason Context triple: [Belle Reeve, lossReason, debts and mortgages]
-
A.
lostStatusReason
chosen
Indicates the reason or cause for which something transitioned into a lost or unsuccessful status.
-
B.
lossType
Indicates the specific category or nature of a loss associated with an entity or event.
-
C.
lostStatus
Indicates that an entity has transitioned into a state of being lost, missing, or no longer in its expected or intended possession or location.
-
D.
failureCause
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
-
E.
loserStatus
Indicates that an entity has been judged or designated as the loser in a particular comparison, contest, or evaluative context.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f630d9c4ec8190af57c75c41ac5b05 |
completed | May 2, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:13 p.m.