Triple
T33077243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archangel Cathedral in Ryazan Kremlin |
E846397
|
entity |
| Predicate | isInFortress |
P28661
|
FINISHED |
| Object | Ryazan Kremlin fortress 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: Ryazan Kremlin fortress complex | Statement: [Archangel Cathedral in Ryazan Kremlin, isInFortress, Ryazan Kremlin fortress complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInFortress Context triple: [Archangel Cathedral in Ryazan Kremlin, isInFortress, Ryazan Kremlin fortress complex]
-
A.
locatedInFortress
chosen
Indicates that an entity is situated within the boundaries or interior of a fortress.
-
B.
containsFortress
Indicates that a location or area includes a fortress within its boundaries.
-
C.
isFortifiedWith
Indicates that one entity has been strengthened, enriched, or supplemented by the addition of another entity.
-
D.
isFortifiedStructureOf
Indicates that one entity is a defensive or fortified structure that protects, encloses, or is associated with another entity.
-
E.
isFortifiedCity
Indicates that a city is strengthened with defensive structures or fortifications, such as walls, ramparts, or similar protective works.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:25 a.m.