Triple
T28086904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rao Jaisal |
E709845
|
entity |
| Predicate | cityFoundedType |
P164028
|
FINISHED |
| Object | desert city-state |
—
|
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: desert city-state | Statement: [Rao Jaisal, cityFoundedType, desert city-state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityFoundedType Context triple: [Rao Jaisal, cityFoundedType, desert city-state]
-
A.
cityFoundedOn
Indicates that a city was established or officially founded on a specific date or point in time.
-
B.
majorCityFounded
Indicates that one entity is a major city and the other is the date or event of its founding.
-
C.
placeFounded
Indicates the location where an entity (such as an organization or institution) was originally established or founded.
-
D.
cityFoundedAround
Indicates that a city was established approximately at, but not exactly on, a specified time or period.
-
E.
locatedInCityFoundedFor
Indicates that something is located in a city that was specifically founded for that thing or for its primary purpose.
- F. None of above. chosen
Provenance (4 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_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 8:55 p.m.