Triple
T16353786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gailani family |
E397120
|
entity |
| Predicate | religiousTitleAssociated |
P502
|
FINISHED |
| Object | Pir |
—
|
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: Pir | Statement: [Gailani family, religiousTitleAssociated, Pir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousTitleAssociated Context triple: [Gailani family, religiousTitleAssociated, Pir]
-
A.
religiousTitle
chosen
Indicates that one entity holds or is referred to by a specific religious rank, honorific, or clerical title in relation to another entity.
-
B.
associatedTitle
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
-
C.
associatedNobleTitle
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
D.
honorificAssociation
Indicates a relationship in which one entity is formally associated with another through a title, honorific, or mark of respect.
-
E.
ecclesiasticalTitleIncludes
Indicates that one ecclesiastical title contains, subsumes, or incorporates another ecclesiastical title as part of its designation or scope.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2facd80dc8190b08f0eecbf787240 |
completed | April 18, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.