Triple
T21500573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government House, Baku |
E530462
|
entity |
| Predicate | hasMonumentality |
P127363
|
FINISHED |
| Object | monumental scale |
—
|
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: monumental scale | Statement: [Government House, Baku, hasMonumentality, monumental scale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonumentality Context triple: [Government House, Baku, hasMonumentality, monumental scale]
-
A.
hasMonumentalFeature
chosen
Indicates that an entity possesses or includes a significant, large-scale, or historically important physical feature or structure.
-
B.
isMonumentalTree
Indicates that a tree is officially recognized as exceptionally significant, typically due to its age, size, rarity, historical, cultural, or ecological importance.
-
C.
isMonumentClassic
Indicates that a monument exemplifies classic or traditional architectural or historical style.
-
D.
significantMonument
Indicates that something is a monument of notable historical, cultural, or symbolic importance.
-
E.
hasNumberOfMonoliths
Indicates the specific count of monoliths associated with a given 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea5be400819093e2b7e145254eab |
completed | April 23, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:24 p.m.