Triple
T15673219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gutenberg discontinuity |
E377370
|
entity |
| Predicate | hasPhysicalPropertyChange |
P119708
|
FINISHED |
| Object | density increase |
—
|
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: density increase | Statement: [Gutenberg discontinuity, hasPhysicalPropertyChange, density increase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhysicalPropertyChange Context triple: [Gutenberg discontinuity, hasPhysicalPropertyChange, density increase]
-
A.
hasKeyChanges
Indicates that one entity undergoes or contains changes in musical key relative to another entity or version.
-
B.
hasResultingChange
Indicates that one entity causes or leads to a specific change or transformation in another entity or state.
-
C.
hasKeyChange
Indicates that an entity undergoes or involves a change of key, such as a modulation or shift in tonal center.
-
D.
changesProperty
Indicates that one entity causes a change in a specific property or attribute of another entity.
-
E.
hasChangedOverTime
Indicates that the state, value, or characteristics of an entity or relationship have become different at some point across a period of time.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f2c996c8190a9ebe0e92608feaa |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:16 a.m.