Triple
T19699938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bidar Kadın |
E473062
|
entity |
| Predicate | type of noble |
P53396
|
FINISHED |
| Object | Ottoman consort |
—
|
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: Ottoman consort | Statement: [Bidar Kadın, type of noble, Ottoman consort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: type of noble Context triple: [Bidar Kadın, type of noble, Ottoman consort]
-
A.
nobleHouseType
Indicates the specific category or classification of a noble house (e.g., royal, ducal, baronial) within a hierarchy or system of nobility.
-
B.
nobleRankType
chosen
Indicates the specific category or level of nobility associated with an entity within a hierarchical noble rank system.
-
C.
hasNoble
Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
-
D.
notableNoble
Indicates that an entity is a noble who is particularly prominent, distinguished, or widely recognized in some notable way.
-
E.
nobilityClass
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b4e01081908f857f219d5d7a24 |
completed | April 20, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.