Triple
T27435540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruqayyah bint Khuwaylid |
E690769
|
entity |
| Predicate | knownInSourcesAs |
P65126
|
FINISHED |
| Object | woman of pre-Islamic Mecca |
—
|
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: woman of pre-Islamic Mecca | Statement: [Ruqayyah bint Khuwaylid, knownInSourcesAs, woman of pre-Islamic Mecca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownInSourcesAs Context triple: [Ruqayyah bint Khuwaylid, knownInSourcesAs, woman of pre-Islamic Mecca]
-
A.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
-
B.
knownAsBy
Indicates that one entity is referred to or recognized by another entity using a particular name or designation.
-
C.
knownIn
chosen
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
D.
isWidelyKnownAs
Indicates that an entity is commonly referred to or recognized by a particular name or label by a broad audience.
-
E.
knowsAs
Indicates that one entity recognizes or refers to another entity by a particular name, alias, or identifier.
- 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_69ef5200fa0481908e28508d6e2c149e |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 12:43 p.m.