Triple
T29221272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Permanent Waves |
E740808
|
entity |
| Predicate | retainsCharacteristic |
P166438
|
FINISHED |
| Object | complex musicianship |
—
|
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: complex musicianship | Statement: [Permanent Waves, retainsCharacteristic, complex musicianship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retainsCharacteristic Context triple: [Permanent Waves, retainsCharacteristic, complex musicianship]
-
A.
protectsCharacteristic
Indicates that one entity safeguards or preserves a particular characteristic or property of another entity.
-
B.
eraCharacteristic
Indicates that a particular quality, feature, or attribute is characteristic of, or typically associated with, a given historical or temporal era.
-
C.
sharedCharacteristic
Indicates that two or more entities possess the same specified attribute or quality.
-
D.
sonCharacteristic
Indicates that a son possesses or exhibits a particular characteristic or attribute in relation to something or someone.
-
E.
recordingCharacteristic
Indicates the specific qualities or attributes of how something is recorded, such as its format, medium, or technical properties.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f664329c8c8190abdb1a68f7362c98 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65fb2ead08190b06677d4d6ea1ea8 |
completed | May 2, 2026, 8:33 p.m. |
Created at: April 28, 2026, 12:15 p.m.