Triple
T31116331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbasi family |
E793097
|
entity |
| Predicate | signedInstrumentOfAccessionTo |
P171163
|
FINISHED |
| Object | Pakistan |
—
|
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: Pakistan | Statement: [Abbasi family, signedInstrumentOfAccessionTo, Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedInstrumentOfAccessionTo Context triple: [Abbasi family, signedInstrumentOfAccessionTo, Pakistan]
-
A.
signedInstrument
Indicates that an entity has formally signed or executed a specific document, contract, or other legal instrument.
-
B.
signedTreatyAt
Indicates that an entity formally entered into and endorsed a treaty at a specific location.
-
C.
signedUnderMonarch
Indicates that a document or agreement was formally signed during the reign or authority of a specific monarch.
-
D.
signatureInstrument
Indicates that an instrument is the primary or most characteristic instrument associated with an entity, such as an artist or performer.
-
E.
annexationInstrument
Indicates the legal or formal instrument (such as a treaty, decree, or law) by which one entity annexes or incorporates another.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c6e0b888190a417ae712c42db0d |
completed | May 3, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f69c2127088190ae92c72461576d3b |
completed | May 3, 2026, 12:51 a.m. |
Created at: April 29, 2026, 9:04 p.m.