Triple
T3320299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thirty Five Ventures |
E69777
|
entity |
| Predicate | notableInvestmentArea |
P45042
|
FINISHED |
| Object | early-stage startups |
—
|
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: early-stage startups | Statement: [Thirty Five Ventures, notableInvestmentArea, early-stage startups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableInvestmentArea Context triple: [Thirty Five Ventures, notableInvestmentArea, early-stage startups]
-
A.
notableRegionOfBusiness
Indicates that a specified geographic region is a significant or primary area in which an entity conducts its business activities.
-
B.
innovationArea
Indicates the thematic or domain-specific field in which an innovation is focused or applied.
-
C.
investsIn
Indicates that one entity allocates resources, typically money or capital, into another entity with the expectation of future returns or benefits.
-
D.
notableIndustry
Indicates that an entity is significantly recognized or prominent within a specified industry or sector.
-
E.
investmentScope
chosen
Indicates the range or boundaries of activities, assets, or sectors that an investment is intended or allowed to cover.
- 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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb13a4e948190841134d6ae6ef432 |
completed | March 8, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.