Triple
T27751798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaisalmer royal lineage |
E701229
|
entity |
| Predicate | accessionPeriod |
P170653
|
FINISHED |
| Object | 1947–1949 |
—
|
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: 1947–1949 | Statement: [Jaisalmer royal lineage, accessionPeriod, 1947–1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessionPeriod Context triple: [Jaisalmer royal lineage, accessionPeriod, 1947–1949]
-
A.
establishedPeriod
Indicates the time span or date range during which something was founded, created, or formally brought into existence.
-
B.
associatedPeriodEnd
Indicates the ending point or final date of the time period with which something is associated.
-
C.
administrationPeriod
Indicates the time span during which an entity is responsible for administering, managing, or governing another entity or resource.
-
D.
archivesPeriod
Indicates that one entity serves as an archival record or repository for materials, information, or events associated with a specified time period.
-
E.
agingPeriod
Indicates the length of time something is allowed or intended to mature or age before reaching its final or usable state.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f693ffa7908190aa4c451b16df9be6 |
completed | May 3, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 27, 2026, 4:20 p.m.