Triple
T7450580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberation Square |
E171996
|
entity |
| Predicate | hasSubjectInArtwork |
P63655
|
FINISHED |
| Object | celebrating civilians |
—
|
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: celebrating civilians | Statement: [Liberation Square, hasSubjectInArtwork, celebrating civilians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubjectInArtwork Context triple: [Liberation Square, hasSubjectInArtwork, celebrating civilians]
-
A.
appearsInWorkOfArt
Indicates that an entity is depicted, represented, or otherwise featured within a particular work of art.
-
B.
associatedWithWorkOfArt
Indicates a relationship in which an entity is connected or related to a specific work of art, such as through creation, contribution, ownership, or contextual association.
-
C.
artworkSubjectHeading
chosen
Indicates that an artwork is associated with a specific subject heading used to categorize or describe its thematic content.
-
D.
includesArtBy
Indicates that one entity contains, features, or presents artwork created by another entity.
-
E.
hasFamousArtwork
Indicates that an entity possesses or is associated with a well-known or widely recognized artwork.
- 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_69c68a66554c8190add75c65942c0317 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f38af3fc8190bc5c57ca89d976bc |
completed | March 27, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c6f039f7248190bb4183f97b605763 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:14 p.m.