Triple
T31441130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahidpur |
E802068
|
entity |
| Predicate | treatySignedAfter |
P100855
|
FINISHED |
| Object | Treaty of Mandeswar |
—
|
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: Treaty of Mandeswar | Statement: [Mahidpur, treatySignedAfter, Treaty of Mandeswar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatySignedAfter Context triple: [Mahidpur, treatySignedAfter, Treaty of Mandeswar]
-
A.
treatyConcludedAfter
chosen
Indicates that one treaty was formally concluded at a later time than another specified treaty.
-
B.
treatySignedYear
Indicates the calendar year in which a specific treaty was formally signed.
-
C.
treatySignedWith
Indicates that a formal treaty or agreement has been officially signed between two parties.
-
D.
treatySignedFor
Indicates that a formal treaty has been signed on behalf of, or in representation of, a particular entity, cause, or subject.
-
E.
treatyDate
Indicates the calendar date on which a treaty is formally agreed upon, signed, or comes into effect between parties.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 30, 2026, 9:05 p.m.