Triple
T28086898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rao Jaisal |
E709845
|
entity |
| Predicate | stateFoundedLocation |
P59586
|
FINISHED |
| Object | present-day Rajasthan, India |
—
|
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: present-day Rajasthan, India | Statement: [Rao Jaisal, stateFoundedLocation, present-day Rajasthan, India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateFoundedLocation Context triple: [Rao Jaisal, stateFoundedLocation, present-day Rajasthan, India]
-
A.
stateFoundedIn
Indicates that a particular state was established or came into existence in a specified year or time period.
-
B.
stateFounded
chosen
Indicates that a particular state was established or created at a specific time or by a specific founding event or agent.
-
C.
capitalOfFoundedState
Indicates that a city serves as the capital of a state (or similar political entity) that it also founded or played a founding role in establishing.
-
D.
cityFounded
Indicates that a particular city was established or came into existence at a specific time or by a specific founding event or agent.
-
E.
cityFoundedOn
Indicates that a city was established or officially founded on a specific date or point in time.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 27, 2026, 8:55 p.m.