Triple
T29180908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consolations |
E739741
|
entity |
| Predicate | alternativeVersionExists |
P127295
|
FINISHED |
| Object | earlier version S.171 |
—
|
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: earlier version S.171 | Statement: [Consolations, alternativeVersionExists, earlier version S.171]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeVersionExists Context triple: [Consolations, alternativeVersionExists, earlier version S.171]
-
A.
containsNewVersionOf
Indicates that one entity includes or embeds a newer version of another entity.
-
B.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
C.
hasEarlierVersion
Indicates that one entity is an earlier or prior version of another entity in a version sequence.
-
D.
alternateVersionTrait
chosen
Indicates that one entity represents an alternative version or variant of another, differing in certain traits or characteristics.
-
E.
hasDifferentVersion
Indicates that one entity exists as a version that differs in some way from another entity.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 28, 2026, 11:57 a.m.