Triple
T30076334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inverted Collar and Tie |
E764329
|
entity |
| Predicate | creatorRoleOfClaesOldenburg |
P195538
|
FINISHED |
| Object | sculptural realization |
—
|
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: sculptural realization | Statement: [Inverted Collar and Tie, creatorRoleOfClaesOldenburg, sculptural realization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creatorRoleOfClaesOldenburg Context triple: [Inverted Collar and Tie, creatorRoleOfClaesOldenburg, sculptural realization]
-
A.
designedBy
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
B.
architecturalSculptor
Indicates a relationship where a person serves as the sculptor responsible for the sculptural elements of an architectural work or structure.
-
C.
sculptorOfMonument
Indicates that one entity is the sculptor who created or designed a particular monument.
-
D.
designerOccupation
Indicates that one entity serves as the professional designer or design specialist for another entity.
-
E.
designerCollaboratedWith
Indicates that a designer worked together with another party on a shared project or creative endeavor.
- F. None of above. chosen
Provenance (4 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69fdd922d73c81908ad3faade247ec16 |
completed | May 8, 2026, 12:37 p.m. |
Created at: April 29, 2026, 7:02 p.m.