Triple
T9669313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historia Nea |
E233984
|
entity |
| Predicate | incompleteReason |
P57902
|
FINISHED |
| Object | lost ending |
—
|
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: lost ending | Statement: [Historia Nea, incompleteReason, lost ending]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incompleteReason Context triple: [Historia Nea, incompleteReason, lost ending]
-
A.
reasonForNotCompletion
chosen
Indicates the explanation or cause for why a task, process, or obligation was not completed.
-
B.
reasonForNonCommencement
Indicates the explanation or cause for why an expected activity, process, or obligation did not begin.
-
C.
failureCause
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
-
D.
isIncompletenessSubjectTo
Indicates that an incompleteness, deficiency, or lack in something is governed, constrained, or determined by a particular condition, rule, or authority.
-
E.
partiallyCompleted
Indicates that an action, process, or task has been started and progressed to some extent, but has not yet been fully completed.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c3d5b3481908c8c66a3528875aa |
completed | April 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.