Triple
T20957903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dignity |
E516149
|
entity |
| Predicate | hasMultipleRecordedVersions |
P136805
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Dignity, hasMultipleRecordedVersions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleRecordedVersions Context triple: [Dignity, hasMultipleRecordedVersions, true]
-
A.
hasMultipleVersions
Indicates that an entity exists in more than one distinct version or revision.
-
B.
hasMultipleRecordings
chosen
Indicates that the same work, performance, or item exists in more than one distinct recorded version.
-
C.
historicalVersion
Indicates that one entity represents an earlier or past version in the history or evolution of another entity.
-
D.
hasVersionCount
Indicates the total number of distinct versions associated with a given entity.
-
E.
recordedVersion
Indicates that one entity is a specific recorded version or recording of another entity (such as a work, performance, or composition).
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb6d6cd48190b83d1ceb1d0f6670 |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 1:29 p.m.