Triple
T11509692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nawabzada |
E272875
|
entity |
| Predicate | titleRankRelation |
P21675
|
FINISHED |
| Object | lower than Nawab |
—
|
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: lower than Nawab | Statement: [Nawabzada, titleRankRelation, lower than Nawab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleRankRelation Context triple: [Nawabzada, titleRankRelation, lower than Nawab]
-
A.
titleRelation
Indicates a relationship where one entity serves as the title, designation, or formal name associated with another entity.
-
B.
titlePositionRelation
chosen
Indicates a relationship specifying how a title is positioned or ordered relative to other titles or elements.
-
C.
canonicalRank
Indicates the standard or officially recognized rank or level assigned to an entity within an ordered hierarchy.
-
D.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
E.
titleHolderRelationship
Indicates a relationship where one entity holds, possesses, or bears a specific title in connection to another entity or context.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db65eb081908613a1002c6a4fb4 |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.