Triple
T20967239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neoclassical realism |
E516398
|
entity |
| Predicate | combinesFeature |
P94092
|
FINISHED |
| Object | idealized forms |
—
|
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: idealized forms | Statement: [Neoclassical realism, combinesFeature, idealized forms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combinesFeature Context triple: [Neoclassical realism, combinesFeature, idealized forms]
-
A.
combinesFeaturesOf
chosen
Indicates that one entity integrates or merges characteristics, attributes, or functionalities originating from multiple other entities.
-
B.
compositionalFeature
Indicates that one entity is a structural or constituent feature that forms part of the composition or makeup of another entity.
-
C.
featuresCompositionBy
Indicates that something includes or presents a composition created by a particular composer or creator.
-
D.
combinedIn
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
-
E.
knownForCombining
Indicates a relationship where one entity is recognized or notable for bringing together or merging multiple elements, entities, or aspects into a unified whole.
- 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_69e6fb9d6b548190af7214ad2468cfbf |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:33 p.m.