Triple
T17533886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koporye Fortress |
E427005
|
entity |
| Predicate | guardedApproachesTo |
P79444
|
FINISHED |
| Object | present-day Saint Petersburg |
—
|
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: present-day Saint Petersburg | Statement: [Koporye Fortress, guardedApproachesTo, present-day Saint Petersburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardedApproachesTo Context triple: [Koporye Fortress, guardedApproachesTo, present-day Saint Petersburg]
-
A.
controlledApproachTo
Indicates a deliberate, regulated, or carefully managed way of proceeding toward or dealing with another entity.
-
B.
protectedApproach
Indicates that one entity safeguards, supports, or enables another entity’s method, path, or manner of proceeding so it can be carried out safely or without interference.
-
C.
controlledApproachesTo
chosen
Indicates that one entity regulates or manages the methods or ways in which another entity can be approached.
-
D.
approaches
Indicates that one entity moves closer in position or state to another entity or reference point.
-
E.
approachOver
Indicates that one entity moves closer to another entity from a position above or higher than it.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4536a0f588190ade91d32308897a0 |
completed | April 19, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.