Triple
T3166251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miles Hendon |
E66217
|
entity |
| Predicate | endures |
P46473
|
FINISHED |
| Object | imprisonment |
—
|
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: imprisonment | Statement: [Miles Hendon, endures, imprisonment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endures Context triple: [Miles Hendon, endures, imprisonment]
-
A.
endurance
Indicates the capacity of an entity to sustain an activity, state, or condition over an extended period without failure or significant loss of performance.
-
B.
tolerates
Indicates that one entity endures, accepts, or allows the presence, behavior, or condition of another entity without intervening to stop or change it.
-
C.
survivesIn
Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
-
D.
perpetuates
Indicates that one entity causes a state, condition, or situation involving another entity to continue or persist over time.
-
E.
reaches
Indicates that one entity extends or moves until it makes contact with, attains, or arrives at another entity or point.
- F. None of above. chosen
Provenance (4 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada643e3e481908f4526d66e36e150 |
completed | March 8, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfe0a948190928f2201d671c654 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada148e9108190b363dd0f1a94ac8e |
completed | March 8, 2026, 4:18 p.m. |
Created at: March 8, 2026, 3:06 p.m.