Triple
T8357872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reval |
E196723
|
entity |
| Predicate | timePeriodAsOfficialNameStart |
P17449
|
FINISHED |
| Object | 13th 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: 13th century | Statement: [Reval, timePeriodAsOfficialNameStart, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodAsOfficialNameStart Context triple: [Reval, timePeriodAsOfficialNameStart, 13th century]
-
A.
timePeriodAsMainHeadquartersStart
Indicates the point in time when a location first became the main headquarters for an entity.
-
B.
formerNamePeriodStart
chosen
Indicates the date or time point when an entity began using a former name that is being recorded.
-
C.
usePeriodStart
Indicates that an entity begins to be used or becomes active starting from a specified time period.
-
D.
narratedPeriodStart
Indicates the point in time at which the narrated or described period begins.
-
E.
timePeriodOrigin
Indicates that one entity is the time period in which the other entity originated or first came into existence.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb806fa5c88190b23b6b3ee9d6ec6d |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:59 p.m.