Triple
T23426316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gazela Bridge (Belgrade) |
E560803
|
entity |
| Predicate | shapeInspiration |
P127058
|
FINISHED |
| Object | slender, gazelle-like form |
—
|
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: slender, gazelle-like form | Statement: [Gazela Bridge (Belgrade), shapeInspiration, slender, gazelle-like form]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shapeInspiration Context triple: [Gazela Bridge (Belgrade), shapeInspiration, slender, gazelle-like form]
-
A.
visualDesignInspiredBy
chosen
Indicates that the visual design of one entity is influenced, modeled, or derived from the visual style or appearance of another entity.
-
B.
themeInspiration
Indicates that one entity serves as the creative source or conceptual basis that inspires or shapes the theme expressed in another entity.
-
C.
designTrend
Indicates a prevailing or emerging stylistic direction or pattern that influences how something is designed over a period of time.
-
D.
shape
Indicates that one entity has a particular geometric or physical form characterized by the other entity.
-
E.
helpsDesign
Indicates that one entity assists or contributes to another entity’s design or design process.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a54a28a08190add6184a44c5005b |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:47 p.m.