Triple
T30360856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zachatskaya Tower |
E772278
|
entity |
| Predicate | isFortifiedStructureOf |
P169112
|
FINISHED |
| Object | Nizhny Novgorod Kremlin complex |
—
|
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: Nizhny Novgorod Kremlin complex | Statement: [Zachatskaya Tower, isFortifiedStructureOf, Nizhny Novgorod Kremlin complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFortifiedStructureOf Context triple: [Zachatskaya Tower, isFortifiedStructureOf, Nizhny Novgorod Kremlin complex]
-
A.
isFortifiedWith
Indicates that one entity has been strengthened, enriched, or supplemented by the addition of another entity.
-
B.
isFortifiedCity
Indicates that a city is strengthened with defensive structures or fortifications, such as walls, ramparts, or similar protective works.
-
C.
fortifiedBuilding
Indicates that a building is strengthened or reinforced for defense against attacks or intrusions.
-
D.
containsFortress
Indicates that a location or area includes a fortress within its boundaries.
-
E.
isFortificationGatewayOf
Indicates that a gateway or entrance structure serves as an access point or defensive portal belonging to a specific fortification.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68242fc208190ae8a9ab1a4bdccfd |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 7:57 p.m.