Triple
T22527042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | أفواه وأرانب |
E556933
|
entity |
| Predicate | الموضوع الفرعي |
P20138
|
FINISHED |
| Object | الفوارق الطبقية في المجتمع المصري |
—
|
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: الفوارق الطبقية في المجتمع المصري | Statement: [أفواه وأرانب, الموضوع الفرعي, الفوارق الطبقية في المجتمع المصري]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: الموضوع الفرعي Context triple: [أفواه وأرانب, الموضوع الفرعي, الفوارق الطبقية في المجتمع المصري]
-
A.
subtheme
chosen
Indicates that one topic or concept functions as a more specific, subordinate theme within a broader overarching theme.
-
B.
minorSector
Indicates that one sector is a subordinate or less significant subdivision within a larger, primary sector.
-
C.
subtitle
Indicates that one work serves as a secondary or explanatory title to another, typically appearing beneath the main title.
-
D.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
E.
secondPartSubject
Indicates that the referenced entity serves as the second part or component of the subject in a composite or multipart relationship.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ed411488190a51320930b9805c2 |
completed | April 29, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:51 p.m.