Triple
T28492641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perm lands |
E721016
|
entity |
| Predicate | timeIncorporatedIntoMuscovy |
P13314
|
FINISHED |
| Object | 15th century |
—
|
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: 15th century | Statement: [Perm lands, timeIncorporatedIntoMuscovy, 15th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeIncorporatedIntoMuscovy Context triple: [Perm lands, timeIncorporatedIntoMuscovy, 15th century]
-
A.
incorporatedIntoMoscow
Indicates that one entity (typically a place or administrative unit) has been formally merged into and made part of Moscow.
-
B.
timePeriodOfInitialRussianControl
Indicates the time span during which Russia first held control or authority over a given entity or territory.
-
C.
historicallyAdoptedBy
Indicates that something (such as a practice, policy, idea, or object) was used or taken up by an entity at some point in the past.
-
D.
timePeriodOfSovietUse
Indicates the span of time during which something was used or operated under Soviet control or by Soviet authorities.
-
E.
laterIncorporatedInto
chosen
Indicates that one entity was subsequently merged into, absorbed by, or formally made part of another entity at a later time.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 3:02 a.m.