Triple
T31806350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sairam District |
E811882
|
entity |
| Predicate | containsHistoricalSettlement |
P101315
|
FINISHED |
| Object | Sairam |
—
|
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: Sairam | Statement: [Sairam District, containsHistoricalSettlement, Sairam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsHistoricalSettlement Context triple: [Sairam District, containsHistoricalSettlement, Sairam]
-
A.
historicalSettlementType
Indicates the type or category of settlement an entity was historically classified as (e.g., village, town, city) during a past period.
-
B.
hasFormerSettlement
Indicates that a location previously contained a settlement that no longer exists or is no longer inhabited.
-
C.
historicallyASettlementOn
Indicates that one place historically existed as a settlement located on or at the site of another place.
-
D.
isOneOfOlderSettlementsIn
chosen
Indicates that an entity is among the earlier or historically older settlements located within a specified area or region.
-
E.
historicalPeriodOfSettlement
Indicates the historical time period during which a particular settlement or habitation of a place occurred.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff9b1ad27081908f8a492396950795 |
completed | May 9, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69ff9a6354c48190ae21070c1424cb7a |
completed | May 9, 2026, 8:34 p.m. |
Created at: April 30, 2026, 11:42 p.m.