Triple
T9961669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rheinturm |
E195583
|
entity |
| Predicate | lightSculptureType |
P73043
|
FINISHED |
| Object | decimal digital clock |
—
|
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: decimal digital clock | Statement: [Rheinturm, lightSculptureType, decimal digital clock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightSculptureType Context triple: [Rheinturm, lightSculptureType, decimal digital clock]
-
A.
featuresSculptureOf
Indicates that one entity includes or displays a sculpture that depicts or represents another entity.
-
B.
artStyleOfEnclosingSculpture
Indicates that one entity specifies the artistic style or aesthetic category of a surrounding or enclosing sculpture associated with another entity.
-
C.
hasSculptureType
Indicates that an entity is associated with a sculpture and specifies the type or category of that sculpture.
-
D.
lightType
chosen
Indicates the specific category or kind of light associated with an entity or lighting setup.
-
E.
assistantSculptor
Indicates a relationship where one entity serves as an assistant to another entity in the role or activity of sculpting.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6d37f0c8190946b958c399f3250 |
completed | April 2, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:47 p.m.