Triple
T9236266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plaza Río de Janeiro |
E221943
|
entity |
| Predicate | hasArtStyleReference |
P68894
|
FINISHED |
| Object | Renaissance sculpture |
—
|
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: Renaissance sculpture | Statement: [Plaza Río de Janeiro, hasArtStyleReference, Renaissance sculpture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtStyleReference Context triple: [Plaza Río de Janeiro, hasArtStyleReference, Renaissance sculpture]
-
A.
hasStyle
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
B.
hasStreetArtStyle
Indicates that something exhibits characteristics or aesthetics associated with a particular style of street art.
-
C.
hasArtFeature
chosen
Indicates that an entity possesses or is characterized by a particular artistic attribute, element, or stylistic feature.
-
D.
hasArtDirection
Indicates that one entity is responsible for or associated with the artistic direction or visual style of another entity.
-
E.
hasSubstyle
Indicates that one style is a more specific or subordinate variant of another style within a hierarchical style structure.
- 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccf09d42488190b8ccb9c4b62fdda8 |
completed | April 1, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:29 p.m.