Triple
T27475404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crypto Valley |
E693441
|
entity |
| Predicate | hasVentureCapital |
P134906
|
FINISHED |
| Object | CV VC |
—
|
NE NERFINISHED |
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: CV VC | Statement: [Crypto Valley, hasVentureCapital, CV VC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVentureCapital Context triple: [Crypto Valley, hasVentureCapital, CV VC]
-
A.
raisedVentureCapital
chosen
Indicates that an entity has obtained funding from venture capital investors.
-
B.
hasNotableEntrepreneurInvolved
Indicates that a notable entrepreneur is involved with, associated with, or plays a significant role in the subject entity or activity.
-
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.
seeksFundingFrom
Indicates that one entity is actively trying to obtain financial support or investment from another entity.
-
E.
hasCoCapital
Indicates that two or more cities share the status and functions of being capital cities of the same political or administrative entity.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 12:56 p.m.