Triple
T11377735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maheshwar |
E269512
|
entity |
| Predicate | periodAsCapital |
P29979
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Maheshwar, periodAsCapital, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodAsCapital Context triple: [Maheshwar, periodAsCapital, 18th century]
-
A.
timeAsCapital
Indicates the period during which a particular city served as the capital of a political entity.
-
B.
periodAsDeFactoCapitalStart
Indicates the point in time when a location begins functioning as the de facto capital, even if not officially designated as such.
-
C.
regionCapitalSince
Indicates that one region has served as the capital of another region continuously since a specified point in time.
-
D.
capitalSince
Indicates that an entity has served as the capital of another entity starting from a specified point in time.
-
E.
servedAsCapitalDuring
chosen
Indicates that a place functioned as the official capital of a political entity during a specified 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_69d6aacca1048190b39dbbc2174616fa |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e7022d508190996f9be0847c2b41 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.