Triple
T25078928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opus Minus |
E628127
|
entity |
| Predicate | workSequenceRelation |
P59025
|
FINISHED |
| Object | shorter companion to Opus Majus |
E628127
|
NE 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: shorter companion to Opus Majus | Statement: [Opus Minus, workSequenceRelation, shorter companion to Opus Majus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workSequenceRelation Context triple: [Opus Minus, workSequenceRelation, shorter companion to Opus Majus]
-
A.
stepRelation
Indicates a relationship where one entity is a step-relative of another, such as a stepparent, stepchild, or stepsibling connection.
-
B.
sequenceInWork
chosen
Indicates that one work appears as a sequential part or installment within a larger overarching work.
-
C.
successorRelationship
Indicates a relationship where one entity directly follows or replaces another in a sequence, order, or role.
-
D.
seriesRelation
Indicates a relationship where one entity is part of, follows from, or is otherwise connected to another within an ordered series or sequence.
-
E.
stageRelation
Indicates a relationship between entities based on their roles, positions, or phases within a staged process or sequence.
- F. None of above.
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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1048e1900c8190a6697997fcb25336 |
completed | May 22, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:21 a.m.