Triple
T30419816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Иоанновский равелин |
E773866
|
entity |
| Predicate | имеетТипПлана |
P8653
|
FINISHED |
| Object | бастионно-равелинная система укреплений |
—
|
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: бастионно-равелинная система укреплений | Statement: [Иоанновский равелин, имеетТипПлана, бастионно-равелинная система укреплений]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: имеетТипПлана Context triple: [Иоанновский равелин, имеетТипПлана, бастионно-равелинная система укреплений]
-
A.
hasPlan
Indicates that an entity possesses or is associated with a specific plan or course of action.
-
B.
hasTypicalPlan
Indicates that there is a standard or commonly followed plan, procedure, or course of action typically associated with the given entity or situation.
-
C.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
-
D.
planType
chosen
Indicates the specific category or kind of plan associated with an entity, such as its level, structure, or intended use.
-
E.
hasBasePlan
Indicates that an entity is associated with or derived from a specified foundational or default plan.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6864cd7548190b3e12ef2fe253ad8 |
completed | May 2, 2026, 11:18 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:05 p.m.