Triple
T26245296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Narya Capital |
E656426
|
entity |
| Predicate | hasNotableCoFounderOccupation |
P151979
|
FINISHED |
| Object | U.S. politician |
—
|
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: U.S. politician | Statement: [Narya Capital, hasNotableCoFounderOccupation, U.S. politician]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableCoFounderOccupation Context triple: [Narya Capital, hasNotableCoFounderOccupation, U.S. politician]
-
A.
notableCoFounderOccupation
Indicates that the co-founder is particularly notable or recognized for having a specific occupation.
-
B.
hasNotableFounder
Indicates that an entity was founded or established by a person or organization considered especially significant or noteworthy.
-
C.
coFounderNotableFor
Indicates that a person is a co-founder of something for which they are notably recognized.
-
D.
hasNotableRoleOfCoFounder
Indicates that an entity holds a notable role specifically as a co-founder of another entity.
-
E.
hasCoFounderBackgroundIn
chosen
Indicates that an entity has a co-founder whose professional or educational background is in a specified field or domain.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 26, 2026, 9:05 p.m.