Triple
T18130881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Shah Zaman |
E434005
|
entity |
| Predicate | birthOrderRelativeToShahryar |
P53369
|
FINISHED |
| Object | younger brother |
—
|
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: younger brother | Statement: [King Shah Zaman, birthOrderRelativeToShahryar, younger brother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthOrderRelativeToShahryar Context triple: [King Shah Zaman, birthOrderRelativeToShahryar, younger brother]
-
A.
positionInFamilyBirthOrder
Indicates the relative order in which a person was born within their family (e.g., first-born, middle child, last-born).
-
B.
relationshipToKingShahryar
chosen
Indicates the type or nature of a person's relationship to King Shahryar, such as familial, marital, or social connection.
-
C.
positionInLineOfSuccessionAtBirth
Indicates the ordinal place an individual held in a defined line of succession at the moment of their birth.
-
D.
birthOrderAmongSonsOfJacobByMother
Indicates the relative birth position of a son among Jacob’s sons born to the same mother.
-
E.
relationToNurJahan
Indicates a relationship or connection that an entity has specifically to Nur Jahan.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddf1e2508190993f65ca137fdf63 |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.