Triple
T27327550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Sumaya bint El Hassan |
E689699
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | technology advocate |
C20510
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: technology advocate Context triple: [Princess Sumaya bint El Hassan, instanceOf, technology advocate]
-
A.
technology activist
A technology activist is an individual who leverages, critiques, and advocates around digital tools and systems to promote social justice, equity, and democratic control over technology.
-
B.
technology evangelist role
chosen
A technology evangelist role focuses on passionately promoting, explaining, and advocating for specific technologies or products to drive adoption, build communities, and influence stakeholders both inside and outside an organization.
-
C.
technology writer
A technology writer researches, interprets, and clearly communicates complex technological concepts, products, and trends to specific audiences through written content such as articles, documentation, and reviews.
-
D.
technology investor
A technology investor is an individual or entity that allocates capital to technology-focused companies or innovations with the expectation of financial returns driven by technological advancement and market growth.
-
E.
technology investor
A technology investor is an individual or entity that allocates capital to technology-focused companies or innovations with the expectation of achieving financial returns through growth, innovation, and market disruption.
- F. None of above.
Provenance (1 batch)
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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 11:36 a.m.