Triple
T26613064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhavnagar State |
E667977
|
entity |
| Predicate | accessionInstrumentSigned |
P173
|
FINISHED |
| Object | 1948 |
—
|
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: 1948 | Statement: [Bhavnagar State, accessionInstrumentSigned, 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessionInstrumentSigned Context triple: [Bhavnagar State, accessionInstrumentSigned, 1948]
-
A.
signatureInstrument
Indicates that an instrument is the primary or most characteristic instrument associated with an entity, such as an artist or performer.
-
B.
signedInstrument
chosen
Indicates that an entity has formally signed or executed a specific document, contract, or other legal instrument.
-
C.
basedOnInstrumentSigned
Indicates that something is established, authorized, or validated on the basis of a formally signed instrument or document.
-
D.
designedSignatureInstrument
Indicates that an entity created or developed a specific signature instrument associated with a particular person or brand.
-
E.
signatureEquipment
Indicates that the object is a distinctive or characteristic piece of equipment closely associated with a particular 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_69ee9cfe16088190a3dddd68e3c7b1ea |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 2:17 a.m.