Triple
T27751812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaisalmer royal lineage |
E701229
|
entity |
| Predicate | presentTitleHolder |
P108380
|
FINISHED |
| Object | titular Maharawal of Jaisalmer |
—
|
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: titular Maharawal of Jaisalmer | Statement: [Jaisalmer royal lineage, presentTitleHolder, titular Maharawal of Jaisalmer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentTitleHolder Context triple: [Jaisalmer royal lineage, presentTitleHolder, titular Maharawal of Jaisalmer]
-
A.
presentHolder
Indicates that one entity is the current possessor or custodian of another entity.
-
B.
currentTitleHolderInShow
Indicates that an entity is the present holder of a specific title or role within a show.
-
C.
includedTitleHolder
Indicates that an entity is recognized or recorded as holding a specified title within a given context or collection.
-
D.
recognizedTitleHolder
chosen
Indicates that an entity is officially acknowledged as holding a particular title or position.
-
E.
titleHolderDuring
Indicates that one entity holds a specific title or position during a defined time period in relation to another entity.
- 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_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 27, 2026, 4:20 p.m.