Triple
T33191385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qabiha |
E849620
|
entity |
| Predicate | spouseOrPartnerRole |
P106611
|
FINISHED |
| Object | consort of caliph |
—
|
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: consort of caliph | Statement: [Qabiha, spouseOrPartnerRole, consort of caliph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOrPartnerRole Context triple: [Qabiha, spouseOrPartnerRole, consort of caliph]
-
A.
spouseOfRole
chosen
Indicates that one role is the spouse (husband, wife, or equivalent marital partner) of another role.
-
B.
spouseType
Indicates the specific role or category of a person within a spousal relationship (e.g., husband, wife, partner).
-
C.
spouseInFamily
Indicates that a person is a spouse (married partner) within the context of a specific family unit.
-
D.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
E.
spouseInQuestion
Indicates that the referenced person is the spouse of the primary entity being discussed or queried.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:29 a.m.