Triple
T11919117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitting series |
E283607
|
entity |
| Predicate | terminatesFor |
P102356
|
FINISHED |
| Object | finite solvable groups |
—
|
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: finite solvable groups | Statement: [Fitting series, terminatesFor, finite solvable groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminatesFor Context triple: [Fitting series, terminatesFor, finite solvable groups]
-
A.
terminatesOn
Indicates that one process, event, or state causes or marks the ending of another at a specific time or condition.
-
B.
usesTerminator
Indicates that one entity employs or applies a specific terminator (such as an end marker, delimiter, or stopping mechanism) in relation to another entity or process.
-
C.
canTerminate
Indicates that one entity has the authority or ability to end or discontinue another entity, process, or relationship.
-
D.
terminalCondition
Indicates the condition or set of conditions under which a process, interaction, or state is considered complete and should terminate.
-
E.
isTerminal
Indicates that an entity represents an endpoint or final state in a process, structure, or sequence, with no further continuation beyond it.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8dff77481908cacf6ad03df34ac |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:44 p.m.