Triple
T32412531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanenstenhawi |
E828262
|
entity |
| Predicate | refusedToReturnTo |
P173548
|
FINISHED |
| Object | New England family |
—
|
NE NERFINISHED |
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: New England family | Statement: [Kanenstenhawi, refusedToReturnTo, New England family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refusedToReturnTo Context triple: [Kanenstenhawi, refusedToReturnTo, New England family]
-
A.
forcedToReturnTo
Indicates that one entity is compelled, against its preference or by external pressure or requirement, to go back to a previous place, state, or situation.
-
B.
refusedToSurrender
Indicates that an entity deliberately chose not to give up control, possession, or submission when requested or demanded by another entity.
-
C.
refusesToLeave
Indicates that an entity is unwilling to depart from a place, situation, or state despite expectation or pressure to do so.
-
D.
didNotReturnTo
chosen
Indicates that an entity failed or chose not to go back to a previous place, state, or situation after having left it.
-
E.
refusedToAppearIn
Indicates that an entity declined or failed to participate in or be present for a specified appearance, event, or role.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 12:53 a.m.