Triple
T15388504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firozkoh |
E367974
|
entity |
| Predicate | timeOfUseAsCapital |
P20655
|
FINISHED |
| Object | 12th–early 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: 12th–early 13th century | Statement: [Firozkoh, timeOfUseAsCapital, 12th–early 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfUseAsCapital Context triple: [Firozkoh, timeOfUseAsCapital, 12th–early 13th century]
-
A.
timeAsCapitalStart
Indicates the point in time when a location first became the capital of a political or administrative entity.
-
B.
usedCapital
Indicates that an entity made use of a particular capital city as its seat of government or primary administrative center.
-
C.
timeAsCapital
chosen
Indicates the period during which a particular city served as the capital of a political entity.
-
D.
periodOfMajorUse
Indicates the time span during which something was primarily or most intensively used.
-
E.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e761b688190893a81246b735b76 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.