Triple
T26498769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stalin Square |
E669357
|
entity |
| Predicate | currentMainMonument |
P145972
|
FINISHED |
| Object | Skanderbeg monument (after renaming as Skanderbeg Square) |
—
|
NE NERFINISHED |
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: Skanderbeg monument (after renaming as Skanderbeg Square) | Statement: [Stalin Square, currentMainMonument, Skanderbeg monument (after renaming as Skanderbeg Square)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentMainMonument Context triple: [Stalin Square, currentMainMonument, Skanderbeg monument (after renaming as Skanderbeg Square)]
-
A.
hasPrimaryMonument
chosen
Indicates that an entity is associated with its main or most significant monument.
-
B.
hasMonumentInCenter
Indicates that a place or area has a monument located at its central point or main focal area.
-
C.
isPublicMonument
Indicates that something is officially designated, accessible, and recognized as a monument in a public space.
-
D.
builtMonument
Indicates that one entity constructed or created a monument in honor of, or related to, another entity.
-
E.
monumentName
Indicates the specific name assigned to a monument associated with an entity.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 27, 2026, 1:11 a.m.