Triple
T15302007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanderbilt Gate at Central Park |
E365810
|
entity |
| Predicate | hasDecorativeMotifs |
P50854
|
FINISHED |
| Object | ornamental ironwork |
—
|
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: ornamental ironwork | Statement: [Vanderbilt Gate at Central Park, hasDecorativeMotifs, ornamental ironwork]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDecorativeMotifs Context triple: [Vanderbilt Gate at Central Park, hasDecorativeMotifs, ornamental ironwork]
-
A.
decorativeComplexity
Indicates the degree or richness of ornamental detail or embellishment present in something.
-
B.
ornamentationStyle
Indicates the decorative design or stylistic approach applied as ornamentation to an entity.
-
C.
hasCarvings
Indicates that one entity features or contains carved designs or engravings on its surface, created by another entity or process.
-
D.
hasFrontCarvings
Indicates that an object or structure features carvings or sculpted details on its front-facing surface.
-
E.
ornamentalFeature
chosen
Indicates that one entity serves as a decorative or embellishing feature of another entity.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ccd575c8190aa43262d3b73ef3c |
completed | April 16, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.