Triple
T14527840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Girl Worth Fighting For |
E340824
|
entity |
| Predicate | endType |
P65191
|
FINISHED |
| Object | abrupt 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: abrupt ending | Statement: [A Girl Worth Fighting For, endType, abrupt ending]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endType Context triple: [A Girl Worth Fighting For, endType, abrupt ending]
-
A.
endOf
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
B.
endTheme
Indicates that something serves as the concluding or final thematic element within a larger sequence, work, or context.
-
C.
endEvent
Indicates that one event or process marks the termination or conclusion of another event or process.
-
D.
finishType
chosen
Indicates the manner or outcome by which an action, process, or event is completed.
-
E.
terminationEndedIn
Indicates that a termination event concluded with a specific outcome or result.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea051bc608190ad4d516c5e7bca43 |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.