Triple
T19051739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adept AI |
E466275
|
entity |
| Predicate | raisedVentureCapital |
P134906
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Adept AI, raisedVentureCapital, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raisedVentureCapital Context triple: [Adept AI, raisedVentureCapital, yes]
-
A.
seeksFundingFrom
Indicates that one entity is actively trying to obtain financial support or investment from another entity.
-
B.
raisedMoneyFor
Indicates that one entity collected or obtained funds specifically to support or benefit another entity, cause, or purpose.
-
C.
supportsVentureStage
Indicates that an entity provides appropriate resources, services, or backing tailored to a specific stage in a venture’s lifecycle (e.g., idea, early, growth, or late stage).
-
D.
earlyInvestorIn
Indicates that one entity invested in another at an early stage of its development or funding lifecycle.
-
E.
raisedWith
Indicates that two or more entities grew up together in the same household or close environment during their formative years.
- F. None of above. chosen
Provenance (4 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc031ff881908e8c68c7aaff3733 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4c0fc3c4c8190abbfe06e1bd3325c |
completed | April 19, 2026, 11:48 a.m. |
Created at: April 10, 2026, 12:03 p.m.