Triple
T27752439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andhra Pradesh Reorganisation Act, 2014 |
E701245
|
entity |
| Predicate | jointCapitalPeriodYears |
P75841
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Andhra Pradesh Reorganisation Act, 2014, jointCapitalPeriodYears, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jointCapitalPeriodYears Context triple: [Andhra Pradesh Reorganisation Act, 2014, jointCapitalPeriodYears, 10]
-
A.
durationInYears
chosen
Indicates the length of time associated with something, measured in whole or fractional years.
-
B.
numberOfPeriods
Indicates the count of distinct time intervals or periods associated with an entity or event.
-
C.
fundingPeriod
Indicates the time span or duration for which funding is allocated, active, or valid within a financial or grant-related relationship.
-
D.
appliesInYears
Indicates that something (such as a rule, condition, or effect) is valid, relevant, or in force during specific years.
-
E.
establishedPeriod
Indicates the time span or date range during which something was founded, created, or formally brought into existence.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63720253c819089ddbecbcbe6401a |
completed | May 2, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:21 p.m.