Triple
T32889032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navabrahma temples |
E841280
|
entity |
| Predicate | stateBeforeFormationOfTelangana |
P30470
|
FINISHED |
| Object | Andhra Pradesh |
—
|
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: Andhra Pradesh | Statement: [Navabrahma temples, stateBeforeFormationOfTelangana, Andhra Pradesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateBeforeFormationOfTelangana Context triple: [Navabrahma temples, stateBeforeFormationOfTelangana, Andhra Pradesh]
-
A.
stateBeforeFormation
chosen
Indicates a relationship where one state or condition existed prior to the formation or creation of another entity or state.
-
B.
significanceInTelangana
Indicates the degree of importance, influence, or relevance that something holds specifically within the context of Telangana.
-
C.
statusAfterCreationOfJharkhand
Indicates the political or administrative status of an entity following the creation of the state of Jharkhand.
-
D.
wasUnionTerritoryAs
Indicates that an entity held the status of a union territory during a specified time or under specified conditions.
-
E.
stateBefore2014
Indicates that a particular state or condition held true prior to the year 2014.
- 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 1, 2026, 1:18 a.m.