Triple
T38394907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Moscow |
E900729
|
entity |
| Predicate | beginsInPeriod |
P56370
|
FINISHED |
| Object | Middle Ages |
—
|
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: Middle Ages | Statement: [History of Moscow, beginsInPeriod, Middle Ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beginsInPeriod Context triple: [History of Moscow, beginsInPeriod, Middle Ages]
-
A.
recordedInPeriodStart
Indicates that an event or record began or was first documented at the start of a specified time period.
-
B.
isSetInTimePeriod
chosen
Indicates that an event, story, or situation takes place within a specified time period.
-
C.
meetsInTimePeriod
Indicates that two entities encounter or come together during a specified time period.
-
D.
acquiredInPeriod
Indicates that one entity was acquired by another within a specified time period.
-
E.
coversPeriodStart
Indicates that the time span or coverage of one entity begins at, or includes, the specified starting point in time of another entity or period.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.