Triple
T2948236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryan Roslansky |
E79554
|
entity |
| Predicate | executiveLevel |
P14125
|
FINISHED |
| Object | C-suite |
—
|
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: C-suite | Statement: [Ryan Roslansky, executiveLevel, C-suite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executiveLevel Context triple: [Ryan Roslansky, executiveLevel, C-suite]
-
A.
designationLevel
chosen
Indicates the specific rank, tier, or level assigned to an entity within a designation or classification system.
-
B.
executiveArticle
Indicates a relationship where an executive is associated with, responsible for, or featured in a specific article.
-
C.
cabinetLevel
Indicates that an official, position, or body holds a status equivalent to or recognized as part of a national cabinet-level rank or authority.
-
D.
executiveBody
Indicates that an entity serves as the executive governing authority or decision-making body for another entity.
-
E.
executiveOfficeInvolved
Indicates that an executive-level office is directly involved in, overseeing, or responsible for the referenced action or 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_69ad8b1089588190b74d9e2505e45762 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98b6cab88190b4dee7e5ec9347e5 |
completed | March 8, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69ad960a70ac8190816b5ae3e8631031 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.