Triple
T28914397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bold and Reckless |
E733315
|
entity |
| Predicate | hasVersionCharacteristic |
P172141
|
FINISHED |
| Object | varies by release |
—
|
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: varies by release | Statement: [Bold and Reckless, hasVersionCharacteristic, varies by release]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVersionCharacteristic Context triple: [Bold and Reckless, hasVersionCharacteristic, varies by release]
-
A.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
B.
hasVersionNumber
Indicates that an entity is associated with a specific version identifier or number.
-
C.
hasVersionType
Indicates that one entity is associated with a specific kind or category of version of another entity.
-
D.
version2Characteristic
Indicates that a specific characteristic or property is associated with version 2 of an entity or artifact.
-
E.
hasVersionStatus
Indicates that an entity is associated with a particular version state or status within its lifecycle or revision history.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 28, 2026, 8:13 a.m.