Triple
T14916181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pedestal Collection |
E371387
|
entity |
| Predicate | hasSupportShape |
P104162
|
FINISHED |
| Object | tulip-like profile |
—
|
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: tulip-like profile | Statement: [Pedestal Collection, hasSupportShape, tulip-like profile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupportShape Context triple: [Pedestal Collection, hasSupportShape, tulip-like profile]
-
A.
hasShapeModel
chosen
Indicates that an entity is associated with a specific geometric or structural shape model that represents its form.
-
B.
hasSquareShape
Indicates that an entity possesses a square geometric shape, typically having four equal sides and four right angles.
-
C.
tieneSoporte
Indicates that one entity provides support, backing, or a supporting structure for another entity.
-
D.
isSupportedFor
Indicates that one entity provides compatibility, assistance, or backing necessary for another entity’s proper use or operation.
-
E.
hasTypeOfSupport
Indicates that one entity provides or is associated with a particular kind or category of support in relation to 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded62038508190946499cd3552990e |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:31 a.m.