Triple
T24279123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gangaikonda Cholapuram |
E605489
|
entity |
| Predicate | capitalUntilCentury |
P17922
|
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: [Gangaikonda Cholapuram, capitalUntilCentury, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalUntilCentury Context triple: [Gangaikonda Cholapuram, capitalUntilCentury, 13th century]
-
A.
capitalDuringEra
chosen
Indicates that a city or settlement served as the capital of a political entity during a specified historical era or time period.
-
B.
capitalDuringExistence
Indicates that a specified place served as the capital of an entity for some or all of the time that entity existed.
-
C.
century
Indicates that an entity is associated with, occurs in, or belongs to a particular 100-year time period.
-
D.
ownedUntilCentury
Indicates that an entity possessed or held ownership of another entity up to, but not necessarily beyond, a specified century.
-
E.
latestCentury
Indicates that the associated time or event occurs in, or belongs to, the most recent century relative to a given reference point.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f5032f48190a027e2d8b382ee79 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.