Triple
T29575483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalapani region |
E753431
|
entity |
| Predicate | disputeOriginPeriod |
P50190
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Kalapani region, disputeOriginPeriod, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disputeOriginPeriod Context triple: [Kalapani region, disputeOriginPeriod, 19th century]
-
A.
disputeDuration
Indicates the length of time over which a dispute persists or remains unresolved between parties.
-
B.
disputeEndTime
Indicates the point in time at which a dispute is considered resolved or officially concluded.
-
C.
hasDisputedPeriod
chosen
Indicates that there exists a time span associated with the subject whose occurrence, duration, or validity is contested or not mutually agreed upon.
-
D.
disputeOrigin
Indicates that there is disagreement or uncertainty about the source, cause, or initial point of something.
-
E.
disputeResolvedIn
Indicates that a particular dispute has been settled or resolved within a specified location, forum, or jurisdiction.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d4a69048190973e14fe6bce5c7f |
completed | May 2, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:02 p.m.