Triple
T7253950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghaus-e Azam |
E157671
|
entity |
| Predicate | epithetCategory |
P23283
|
FINISHED |
| Object | saintly title |
—
|
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: saintly title | Statement: [Ghaus-e Azam, epithetCategory, saintly title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: epithetCategory Context triple: [Ghaus-e Azam, epithetCategory, saintly title]
-
A.
epithetOrTitle
chosen
Indicates that one entity serves as an epithet, honorific, or formal title used to designate or characterize another entity.
-
B.
languageOfEpithet
Indicates the language in which an epithet (such as a descriptive or honorary title) is expressed.
-
C.
epithetOfPantheon
Indicates that one term is used as an epithet or honorific title specifically for a deity or figure within a particular pantheon.
-
D.
epithetOfDynasty
Indicates that a particular epithet (honorific or descriptive title) is associated with and used to refer to a specific dynasty.
-
E.
eponymFor
Indicates that one entity gives its name to another entity, which is then named after it.
- 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea9f55b4819081a43e7a01eda154 |
completed | March 27, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:56 p.m.