Triple
T20310239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryker |
E510217
|
entity |
| Predicate | endingPattern |
P58297
|
FINISHED |
| Object | ends with '-er' |
—
|
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: ends with '-er' | Statement: [Ryker, endingPattern, ends with '-er']
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endingPattern Context triple: [Ryker, endingPattern, ends with '-er']
-
A.
endedWith
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
B.
endingStyle
Indicates the manner or stylistic form in which something concludes or is brought to an end.
-
C.
stopsPattern
Indicates that one entity halts, interrupts, or prevents the continuation of a recurring or structured pattern involving another entity.
-
D.
endingDescribedBy
chosen
Indicates that the conclusion or final part of something is characterized, explained, or detailed by a particular description or representation.
-
E.
alternateEnding
Indicates that one version of a work provides a different conclusion or final sequence of events compared to the original or primary ending.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e677436af88190a046c44fa45b68b4 |
completed | April 20, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:19 a.m.