Triple
T5241048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Nystad |
E118339
|
entity |
| Predicate | confirmedPossessionOf |
P27902
|
FINISHED |
| Object | Saint Petersburg by Russia |
—
|
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: Saint Petersburg by Russia | Statement: [Treaty of Nystad, confirmedPossessionOf, Saint Petersburg by Russia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confirmedPossessionOf Context triple: [Treaty of Nystad, confirmedPossessionOf, Saint Petersburg by Russia]
-
A.
recognizedPossession
chosen
Indicates that an entity formally acknowledges or accepts another entity’s ownership or control over something.
-
B.
ownedIn
Indicates that one entity possesses or holds legal or recognized ownership of another entity within a specific context, domain, or scope.
-
C.
attestedAs
Indicates that something is documented, recorded, or certified as having a particular status, form, or property.
-
D.
claimed
Indicates that an entity has asserted or stated something as true, often without definitive proof or verification.
-
E.
possessedItem
Indicates that one entity owns, holds, or has control over another entity as a possession.
- 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_69bd4467db0881909b3b0982df32cc8f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b2c50508190b84bab216c30cbfe |
completed | March 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.